メニュー
Catch up on uncommitted work — read all uncommitted git changes (staged, unstaged, untracked) into the conversation to establish context. Use when resuming work or when the user runs /catchup.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Expert guidance for ffuf web fuzzing during penetration testing, including authenticated fuzzing with raw requests, auto-calibration, and result analysis
Bring a JavaScript repo up to the standard Code Quality Playbook baseline (Prettier, ESLint ratchet, husky + lint-staged, CI lint gate, optional JSDoc typecheck) idempotently — present pieces are skipped, missing ones are added — then optionally migrate the repo from npm to pnpm (lockfile import, packageManager pin, build-script allow-list, Firebase functions-framework fix, npm cleanup). Manual, global. Use only when the user runs /code-quality.
Create git commits for staged and unstaged changes using the emoji commit-message format, with optional push. Use when the user wants to commit or check in changes, or runs /commit.
Execute one complete unit of work end-to-end through tight feedback loops — understand it, plan it, build it, validate it, commit it — never advancing a phase until its feedback signal is green. Manual and global: runs only when the user invokes /do-work or another skill explicitly hands it a scoped unit of work. Use to "do the work", "execute this task/plan/issue", "build and validate and commit", or as the execution engine other planning skills delegate to.
Set up Playwright E2E testing framework for any project — auto-detects stack, auth, routes, and selectors
Generate a structured development epic through an interactive, phase-by-phase approval workflow that breaks a large piece of work into tasks. Use to create an epic, break down a large feature, or when the user runs /epic.
| name | catchup |
| description | Catch up on uncommitted work — read all uncommitted git changes (staged, unstaged, untracked) into the conversation to establish context. Use when resuming work or when the user runs /catchup. |
Read all uncommitted git changes into the conversation to provide context.
Run these commands in parallel to understand the current state:
git status to see all changed files (never use -uall flag)git diff to see unstaged changesgit diff --cached to see staged changesgit log --oneline -5 to see recent commits for contextSummarize the changes:
If there are no uncommitted changes, inform the user the working tree is clean.
Ask if the user wants you to read any specific files in full for more context.
Provide a clear summary like: