Review a Git diff against repository standards and its originating requirements. Use for pull requests, branches, work-in-progress changes, or changes since a commit, tag, or merge-base.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design or improve module interfaces using deep-module heuristics. Use when deciding where a seam belongs, reducing caller-facing complexity, improving testability or navigability, or comparing module designs.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Sets up an `## Agent skills` block in AGENTS.md/CLAUDE.md and `docs/agents/` so the engineering skills know this repo's issue tracker (GitHub or local markdown), triage label vocabulary, and domain doc layout. Run before first use of `to-issues`, `to-prd`, `triage`, `diagnose`, `tdd`, `improve-codebase-architecture`, or `zoom-out` — or if those skills appear to be missing context about the issue tracker, triage labels, or domain docs.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Discover installable agent skills from ctx's shipped Skills.sh catalog, the Skills.sh search API, and the npx skills CLI. Use when a user asks whether a skill exists, wants to add/update a skill, or needs a repeatable procedure for finding candidate skills safely.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Set up Claude Code hooks to block dangerous git commands (push, reset --hard, clean, branch -D, etc.) before they execute. Use when user wants to prevent destructive git operations, add git safety hooks, or block git push/reset in Claude Code.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Migrate test files from `as` type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, wants to replace `as` in tests, or needs partial test data.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Interactive QA session where user reports bugs or issues conversationally, and the agent files GitHub issues. Explores the codebase in the background for context and domain language. Use when user wants to report bugs, do QA, file issues conversationally, or mentions "QA session".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create or review an AGENTS.md file so coding agents get stable repo-local instructions: environment setup, testing, style, security boundaries, PR policy, and handoff rules. Use when a repo lacks durable agent guidance or when a custom harness needs a predictable context file.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Recommend the smallest Matt Pocock skill or short skill sequence that fits the user's current goal.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Diagnose hard bugs and performance regressions with reproducible evidence, focused hypotheses, and proportional instrumentation. Use when something is broken, failing, throwing, intermittently wrong, or unexpectedly slow.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Keeps README badge + inline counts in sync with the real number of skills, agents, graph nodes/edges, communities, converted pipelines, and test inventory. Runs automatically on every commit via a git pre-commit hook. Use when the README drifts from reality or before publishing a release.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Show real token usage and estimated savings for the current session. Reads directly from the Claude Code session log — no AI estimation. Triggers on /caveman-stats. Output is injected by the mode-tracker hook; the model itself does not compute the numbers.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Clarify domain concepts, language, boundaries, and durable architectural decisions. Use when terminology is ambiguous, the user is shaping a domain model, or a design depends on resolving what concepts mean.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generate multiple radically different interface designs for a module using parallel sub-agents. Use when user wants to design an API, explore interface options, compare module shapes, or mentions "design it twice".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create new agent skills with proper structure, progressive disclosure, and bundled resources. Use when user wants to create, write, or build a new skill.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Select proportional validation for changes or reviews in the ctx repository. Use before handing off material code, workflow, migration, documentation, security, packaging, or release changes; before a PR; or when asked whether a change is adequately tested. Do not use for pure questions with no changed artifact.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create a detailed refactor plan with tiny commits via user interview, then file it as a GitHub issue. Use when user wants to plan a refactor, create a refactoring RFC, or break a refactor into safe incremental steps.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/PRD asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to "review since X".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.