菜单
Weekly engineering review. Summarizes what changed (commits/PRs) and what we learned (lessons), then grows the pattern library. Use when asked for a weekly review, weekly digest, "what changed this week", or "evolve patterns".
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | weekly-review |
| description | Weekly engineering review. Summarizes what changed (commits/PRs) and what we learned (lessons), then grows the pattern library. Use when asked for a weekly review, weekly digest, "what changed this week", or "evolve patterns". |
Combines the engineering digest with pattern evolution into a single weekly ritual. Part 1 answers "what happened?", Part 2 answers "what did we learn?", and they cross-reference each other.
find <folder> -maxdepth 3 -name .git -type d) and aggregate per-repo,
then cross-reference patterns across all repos.Always filter git log by --author="$(git config user.email)" so team
commits don't drown out your own work. In multi-repo mode, run git config
inside each repo so per-repo identities are respected.
Gather data. For each repo in scope, collect commits from the last 7 days filtered by author. Read the diff of each significant commit or PR. If a repo has zero commits after filtering, note the week was quiet there and skip to the next one.
Analyze and cluster. Group related commits into themes with user-facing or system impact. Flag security changes and areas with missing test coverage or rollout risk.
Compose the digest. Output Key Changes and Watchlist sections, grouped by repo in multi-repo mode. Skip repos with no commits. If no commits across any repo in scope, state that and skip to Part 2.
Read learning sources:
tasks/lessons.md for recurring corrections (same area, 2+ times)..claude/skills/railspilot-staff-review/patterns.md for existing
coverage and ID numbering.Cross-reference digest with lessons. A bug-fix theme plus a correction in the same area is a strong pattern candidate. For commits that touched areas with known pattern violations, flag them.
Identify and draft pattern candidates. Follow the existing format and categories in patterns.md, or propose new ones. If the same pattern keeps getting violated in lessons.md, suggest strengthening its Detection hints or promoting it to CLAUDE.md.
Present everything in a single report:
Ask which candidates to apply.
Apply approved changes and clean up promoted lessons (same rule as
/rails-learn step 6: delete from tasks/lessons.md after promotion).
/rails-learn runs has accumulated lessons.Reviews the current branch diff for bugs, edge cases, performance regressions, and behavior interactions. Use when asked for a code review, "review my changes", "check this code", or "anything wrong with this". This is a quick, focused review — for comprehensive multi-agent reviews, use full-code-review instead.
Analyzes code against staff-engineer patterns (security, architecture, simplicity, completeness, hygiene). Use when asked for a staff or senior code review, "staff review", "pattern review", or "review this like a staff engineer". This is the most thorough single-agent review — for multi-agent reviews, use full-code-review.
Generate monthly client progress reports for RailsPilot. Uses gh CLI to list the user's merged PRs, applies feature sizing rules, and drafts a numbered-list email. Use when asked for a monthly progress report, client delivery summary, or "progress report for [Month]".
Quick-reference card for all ponytail modes, skills, and commands. One-shot display, not a persistent mode. Trigger: /ponytail-help, "ponytail help", "what ponytail commands", "how do I use ponytail".
Write a warm, human-to-human written response (handoffs, status updates, testing notes for QA, sign-off requests, confirming assumptions before merging, or escalating an open question). Use when the user asks to draft a response, reply to a thread, write a handoff, send testing notes, ask the team to confirm something, phrase a Slack or PR comment, or convert dev-flavored notes into a message a teammate would actually enjoy reading.
Trim editorial bloat from technical docs (integration writeups, ADRs, investigation notes, READMEs). Proposes a unified diff with per-cut rationale and waits for approval. Use when asked to "trim this doc", "tighten this writeup", "filter pass on X.md", "prune the doc", or "cut the slop from this writeup".