메뉴
Sprint retrospective — analyzes git velocity, commit patterns, test health, and shipping cadence. Use after a sprint, at the end of the week, or when the user wants to reflect on progress.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Build a regression + eval harness for AI-written code and AI features. Generates characterization tests that lock current behavior before a refactor, scaffolds a Promptfoo eval suite for chatbots/RAG/classifiers, and wires it into the ship-gate. Use when the user wants evals, regression tests for AI code, to stop AI features drifting, or to test an LLM feature.
Run security audit — dependency vulnerabilities, secret scanning, OWASP pattern detection, HTTP headers. Use when user wants to harden their project.
Accessibility audit + auto-fix (WCAG 2.2 A/AA). Scans built/static HTML for screen-reader, keyboard, and structure failures, fixes the deterministic ones, and escalates to a rendered scan for contrast and focus. Use when the user wants to check or improve accessibility, fix WCAG issues, or pass an a11y review.
Turn the /ship scorecard into a blocking, config-as-code quality gate. Sets per-category score thresholds, hard-fails on leaked secrets or critical findings, and wires the gate into a pre-push hook and CI so nothing below the bar merges. Use when the user wants a merge gate, CI quality gate, pre-push check, or to enforce ship-readiness.
Post-deploy canary monitoring — checks site health, detects regressions, monitors for errors after deployment. Use after deploying to verify production is healthy.
Code review with principal-engineer-level depth. Reviews for correctness, performance, security, maintainability, and architecture. Use when completing tasks, reviewing PRs, or before merging.
| name | retro |
| description | Sprint retrospective — analyzes git velocity, commit patterns, test health, and shipping cadence. Use after a sprint, at the end of the week, or when the user wants to reflect on progress. |
| argument-hint | <days-back> |
| allowed-tools | Bash, Read, Grep, Glob |
Retrospectives turn shipping data into actionable insights. This skill analyzes your git history, commit patterns, test health, and shipping velocity to surface what's working and what needs attention.
Announce at start: "I'm running a sprint retrospective on this project."
Run the retro analyzer:
node ${CLAUDE_PLUGIN_ROOT}/tools/retro-analyzer.mjs <project-directory> --days 7
For custom date ranges:
node ${CLAUDE_PLUGIN_ROOT}/tools/retro-analyzer.mjs <project-directory> --since 2026-03-24
Format the data as a clear, actionable report:
+===========================================+
| S P R I N T R E T R O |
+===========================================+
| Period Mar 24 – Mar 31 |
| Commits 47 |
| Lines Added 2,341 |
| Lines Removed 892 |
| Net Change +1,449 |
| Authors 1 |
+===========================================+
Show the distribution of commit types (features, fixes, refactors, tests, docs, chores) as a visual breakdown. Highlight the feature-to-fix ratio — a healthy project ships more features than fixes.
List the most-changed files. Files with excessive churn may need to be split into smaller modules.
Based on the data, surface:
What went well:
What needs attention:
Action items:
/tdd for the untested module")If the project has learnings (from /learn), search for relevant context:
node ${CLAUDE_PLUGIN_ROOT}/tools/learnings-manager.mjs search --query "sprint"
node ${CLAUDE_PLUGIN_ROOT}/tools/learnings-manager.mjs search --query "debugging"
Incorporate past learnings into recommendations.
For founders running multiple projects, run retros across all of them:
node ${CLAUDE_PLUGIN_ROOT}/tools/retro-analyzer.mjs ~/project-a --days 7
node ${CLAUDE_PLUGIN_ROOT}/tools/retro-analyzer.mjs ~/project-b --days 7
Compare velocity across projects to understand where time is being spent.
The retrospective should be concise and actionable — not a data dump. Lead with insights, support with data. The goal is to help the user ship better next week.