Menú
Reusable prompt snippets for Claude and Gemini. Use for adding snippets, renaming slugs, or editing snippet folder structure.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
| name | aitk-snippets |
| description | Reusable prompt snippets for Claude and Gemini. Use for adding snippets, renaming slugs, or editing snippet folder structure. |
Read .claude/context/snippets.md for system overview, categories, and structure before editing.
aitk snippets create to add a snippet. To add manually: create a .md file in the correct folder.snippets/aitk/. Reserve snippets/claude/ for snippets a target project would invoke.snippets/. One-shot-per-project audit, migration, or bootstrap prompts go to external notes.snippets/snippets.toml defines virtual presets (curated slug lists) that aitk snippets install resolves alongside folder-derived categories. Folder-based categories (base, claude) need no toml entry.
essentials is the default aitk init install. Keep it tight: only snippets the user reaches for in nearly every session.claude/feature-recap). They resolve to .claude/snippets/<slug>.md on install.snippets.toml and a row in .claude/context/snippets.md.When adding a snippet:
snippets/{category}/{name}.md (or snippets/{name}.md for base).claude/context/snippets.md categories table and snippets tableessentials, add it to snippets/snippets.tomlWhen renaming a snippet:
snippets.toml preset entries that reference the old slug.claude/context/snippets.md: system overview, categories, CLIstandards/bundled/snippets.md: what a snippet is, invocation channels, use patterns, authoring conventionsPulls review findings and CI status on the current branch's open PR, fixes each in the working tree, refreshes any stale `.claude/` docs, replies with a summary comment, and pushes a follow-up commit. The worker's return leg after `claude-pr-review`. Use when asked to "address the review", "fix the PR comments", "respond to review", or after an orchestrator posts findings. Do NOT use to write a review. That is `claude-pr-review`.
Ships a small self-review edit on the current PR branch by staging, committing, pushing, and syncing the open PR, replying on the PR when it carries review comments. Use when asked to "ship a followup", "push the PR fix", "followup", or "commit and push this small change". Do NOT use when there is no open PR for the branch (use git-ship instead).
Claude skill structure and authoring rules
Chains implement → verify → review → ship after a feature plan is approved. Reads the plan for the current branch, runs the full pipeline in one session, and stops on any failure or non-minor review finding. Use when asked to "autoship", "ship this feature end to end", or "run the chain". Do NOT auto-trigger. Requires an approved plan file.
Asserts the orchestrator role for the current session and holds the build loop, dispatching to the roadmap, feature, review, and worktree skills. Use when asked to "be the orchestrator", "run the orchestrator", "orchestrate this project", or to set up the control session for parallel feature builds. Do NOT build features or merge PRs in this session.
Reviews an open pull request from an independent session and posts findings as a review comment on the PR. Reads project docs and the roadmap for cross-feature context a self-review lacks. Use when asked to "review the PR", "review this feature's PR", "post a PR review", or acting as the orchestrator reviewing a worker's PR. Do NOT use to review local uncommitted changes. That is `claude-review`.