開発のスキル

Add a community extension to the Spec Kit catalog from a GitHub issue submission. USE FOR: processing extension submission issues, validating catalog entries, updating catalog.community.json and docs/community/extensions.md, creating PRs. DO NOT USE FOR: creating new extensions from scratch, or first-party extension work.

日本語の概要は準備中です。原文の説明を表示しています。

Reviews Spec Kit code changes for consistency with applicable design documents, positive and negative test coverage, regression evidence for bug fixes, and consistent repository terminology. Use when reviewing a diff or pull request. Do not use for implementing changes or posting GitHub review actions.

日本語の概要は準備中です。原文の説明を表示しています。

Use when asked to debug, fix a bug, investigate an error, or do root cause analysis, and when users report errors, stack traces, unexpected behavior, or say something stopped working.

日本語の概要は準備中です。原文の説明を表示しています。

Keep gbrain current with this repo's code and refresh agent search guidance in CLAUDE.md. (gstack)

日本語の概要は準備中です。原文の説明を表示しています。

Set up gbrain for this coding agent: install the CLI, initialize a local PGLite or Supabase brain, register MCP, capture per-remote trust policy. (gstack)

日本語の概要は準備中です。原文の説明を表示しています。

Find worthwhile shared-code extractions in recent work. (gstack)

日本語の概要は準備中です。原文の説明を表示しています。

OpenAI Codex CLI wrapper — three modes. (gstack)

日本語の概要は準備中です。原文の説明を表示しています。

Remove the DebugBridge SPM package and all #if DEBUG wiring from an iOS app. (gstack)

日本語の概要は準備中です。原文の説明を表示しています。

Systematic debugging with root cause investigation. (gstack)

日本語の概要は準備中です。原文の説明を表示しています。

Regenerate the iOS debug bridge against the latest upstream gstack templates. (gstack)

日本語の概要は準備中です。原文の説明を表示しています。

Perform a read-only, defect-first review of a specified code change and return every actionable finding. Use when another agent delegates review of uncommitted changes, a base-branch diff, a commit, or custom review instructions.

日本語の概要は準備中です。原文の説明を表示しています。

Create or update a Codex skill with appropriately scoped instructions and any needed supporting resources.

日本語の概要は準備中です。原文の説明を表示しています。

Install Codex skills into $CODEX_HOME/skills from a curated list or a GitHub repo path. Use when a user asks to list installable skills, install a curated skill, or install a skill from another repo (including private repos).

日本語の概要は準備中です。原文の説明を表示しています。

Reverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.

日本語の概要は準備中です。原文の説明を表示しています。

Restructure code while preserving behavior. Use for extraction, consolidation, ownership moves, or cleanup where verification must bracket structural edits.

日本語の概要は準備中です。原文の説明を表示しています。

Show recorded output and cache-read token usage and mode attribution for the current Claude Code session, or locate the host's native usage report. Trigger: /caveman-stats.

日本語の概要は準備中です。原文の説明を表示しています。

Compressed code review - one line per finding with location, problem and fix. Use for /caveman-review, "review this PR", or "review the diff".

日本語の概要は準備中です。原文の説明を表示しています。

When to delegate to `cavecrew-investigator` (locate code), `cavecrew-builder` (1-2 file edit) or `cavecrew-reviewer` (diff review) instead of working inline or using `Explore`. Their output is compressed, so main context lasts longer.

日本語の概要は準備中です。原文の説明を表示しています。

Optimizes application performance across frontend, backend, queries, and databases. Use when performance requirements exist, when you suspect performance regressions, when Core Web Vitals or load times need improvement, when N+1 query patterns need fixing, or when profiling reveals bottlenecks.

日本語の概要は準備中です。原文の説明を表示しています。

Conducts multi-axis code review. Use before merging any change. Use when reviewing code written by yourself, another agent, or a human. Use when you need to assess code quality across multiple dimensions before it enters the main branch. Use when asked to review a diff or a pull request, even when the diff is pasted inline.

日本語の概要は準備中です。原文の説明を表示しています。

Simplifies code for clarity. Use when refactoring code for clarity without changing behavior. Use when code works but is harder to read, maintain, or extend than it should be. Use when reviewing code that has accumulated unnecessary complexity.

日本語の概要は準備中です。原文の説明を表示しています。

Creates specs before coding. Use when starting a new project, feature, or significant change and no specification exists yet. Use when drafting a PRD or requirements document with objectives and scope, or when requirements are unclear, ambiguous, or only exist as a vague idea. Use when a single requirement spans several independently testable capabilities and needs decomposing into a capability map of modules before specifying.

日本語の概要は準備中です。原文の説明を表示しています。

Guides systematic root-cause debugging. Use when tests fail, builds break, something that worked yesterday broke, behavior doesn't match expectations, or you encounter any unexpected error. Use when you need to figure out what broke and why — a systematic approach to finding and fixing the root cause rather than guessing.

日本語の概要は準備中です。原文の説明を表示しています。

Read an existing repository's structure into the project cwd as a normalised snapshot the agent can analyse without re-walking the tree on every turn.

日本語の概要は準備中です。原文の説明を表示しています。