breakdown-pr
01Skill Claude Code
Plan and optionally execute a large pull request split into small stacked PRs. Use for PR breakdown, split PR, stacked PRs, branch decomposition, oversized diffs, gh-stack, Graphite, git range-diff, or PR too large.
Skill Claude Code
Plan and optionally execute a large pull request split into small stacked PRs. Use for PR breakdown, split PR, stacked PRs, branch decomposition, oversized diffs, gh-stack, Graphite, git range-diff, or PR too large.
Skill Claude Code
Orchestrate Claude Code bundled skills after implementation. Use only when the main agent is Claude Code or another Claude agent with Claude Code skills available and an implementation report exists.
Skill Claude Code
Multi-axis, review-only code review of a diff across six axes — request achievement, correctness, readability/simplicity, architecture, security, and performance — with severity-labelled findings. TRIGGER: invoked by a HarnessFlow workflow's post-implementation review step when the request header is codereview: local.…
Skill Claude Code
Simplify code for clarity while preserving exact behavior — reduce nesting, split long functions, remove redundancy and dead code, and fix unclear names. TRIGGER: invoked by a HarnessFlow workflow's post-implementation review step when the request header is simplify: local. Not a planning-time skill.
Skill Claude Code
Generate MY "last week update report": summarize the past 7 days of git commit history into a short, user-facing weekly update. TRIGGER ONLY when the user explicitly asks to generate their last week / weekly update report (e.g. "generate my last week update report", "make my weekly update", "what did I ship last…
Skill Claude Code
Generate a structured, pipeline-and-component-oriented README.md for a repository, grounded in its actual source and repoinfo context rather than a generic template. Produces, in order: a short goal paragraph, an entry-point-to-outcome pipeline overview covering every component at a high level, a per-component and…
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: