القائمة
Use when the user asks to clean up, squash, reorganize, or rewrite commit history on the current branch before a PR. Groups messy commits into logical, reviewable units while preserving meaningful history.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when the user asks to analyze, audit, review, or check code quality across the project. Performs full codebase analysis — detects bad patterns, security flaws, performance issues, misconfigurations — and generates a prioritized report in docs/ANALYSIS-{date}.md.
Use when the user asks to analyze, document, inspect, or understand the database schema. Connects to the live database (Docker or direct) and reads ORM code to produce comprehensive docs/DB.md with tables, relations, indexes, and query patterns.
Use when the user wants to set up, create, inspect, or manage PolyForge nocturnal routines — the banked embers that keep the forge working after hours. Subcommands: "embers light" installs/configures nightly routines, "embers cast" creates a custom routine, "embers watch" inspects logs/telemetry, "embers tend" lists/suspends/resumes/deletes/runs them.
Use when the user asks to generate, update, or refresh project documentation, CLAUDE.md, context files, or scoped rules. Creates Claude-optimized documentation with a short CLAUDE.md (<200 lines), detailed docs/CONTEXT.md, and path-scoped rules.
Use when the user asks to review a PR, check a pull request, review a GitHub issue, review a Jira ticket, look at changes before merge, or audit code quality. Auto-detects the item type (PR, GitHub issue, Jira ticket) and adapts the review accordingly.
Use when the user asks to initialize, set up, or configure PolyForge for a project, or when starting work on a project with no .claude/polyforge.json. Scans the project, detects stack and architecture, and generates optimized configuration interactively.
| name | fold |
| description | Use when the user asks to clean up, squash, reorganize, or rewrite commit history on the current branch before a PR. Groups messy commits into logical, reviewable units while preserving meaningful history. |
You are PolyForge's commit organizer. Turn a messy branch into clean, logical commits.
/fold Clean up current branch against main/master
/fold origin/develop Clean up against a specific base branch
git merge-base HEAD origin/main || git merge-base HEAD origin/master
git log --oneline --reverse origin/main..HEAD
git diff origin/main..HEAD --stat
Under 3 commits → "Only {N} commits — nothing to clean up." Stop.
Over 2000 lines diff: Spawn [model: sonnet] subagent for per-file categorization → returns JSON: [{ "file": "", "category": "" }]
Group: Schema/Infrastructure | Core Implementation | API/Interface | Tests | Documentation | Cleanup Cleanup commits always absorbed into parent — never standalone.
Current: 18 commits → Proposed: 4 commits
1. feat(db): add user preferences migration + model
← squashes: "add migration", "add model", "fix lint"
2. feat(api): add preferences endpoints + service
← squashes: "add service", "add controller", "fix type error"
Call AskUserQuestion — "How should I proceed?" with options: "Apply" / "Show diffs per group" / "Adjust grouping" / "Cancel" / "Other". See @skills/shared/common-patterns.md § "User Questions — AskUserQuestion ONLY".
git reset --soft $(git merge-base HEAD origin/main)
git add <schema files> && git commit -m "feat(db): ..."
git add <core files> && git commit -m "feat(api): ..."
git diff origin/main..HEAD --stat # must match pre-squash stat
{test command}
Show: before/after commit count, diff identical confirmation, test status.
Call AskUserQuestion — "Push with --force-with-lease?" with options: "Push now" / "Skip push" / "Other" (only if remote branch exists).
If PR exists: preserve template structure, update only summary/changes.
type(scope): short description + key details--force-with-lease not --force