agentleFS
Sign inStart free
AirMileAirMile/claude-config/skills/core-finalize/SKILL.md

core-finalize

Skill0 starsChanged 4 months agoMITView on GitHub

Merge or clean up a feature worktree. Use with /core-finalize.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Not for: regular commits (use /core-commit), pulling remote changes (use /core-pull), creating new branches.

    line 23
  2. Very specific:

    No argument, currently in a worktree: use current branch name (strip worktree- prefix if present).

    line 32

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Finalize

Integrate or clean up a finished feature worktree. Detects whether the branch was already merged via a PR (cleanup-only) or needs a local merge (solo), then removes the worktree and branch.

Trigger: /core-finalize or /core-finalize [feature-name]

When to Use

  • Feature worktree exists but the pipeline skill's PHASE Finalize was skipped or not reached
  • Orphan worktree from an earlier session (hotfix, abandoned build, etc.)
  • Manual recovery when a pipeline skill is not involved

Not for: regular commits (use /core-commit), pulling remote changes (use /core-pull), creating new branches.

Workflow

Follow shared/FINALIZE.md end-to-end.

Feature-name resolution

  • Argument provided (/core-finalize auth): pass feature-name = "auth" to FINALIZE.md.
  • No argument, currently in a worktree: use current branch name (strip worktree- prefix if present).
  • No argument, on main: list all open worktree-* branches via git worktree list --porcelain. Use AskUserQuestion to pick:
    • header: "Worktree"
    • question: "Which worktree do you want to finalize?"
    • options: one per open worktree — {branch} ({short-path}, {N} commits ahead)
    • 0 candidates → exit: "No active worktrees found."

Pass resolved feature-name to FINALIZE.md with mode: auto.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free