agentleFS
Sign inStart free
roronoazoroshao369roronoazoroshao369/vibe-coding-os/skills/core/finishing-a-development-branch/SKILL.md

finishing-a-development-branch

Skill1 starsChanged 5 months agoMITView on GitHub

Close a branch cleanly with verified status, review readiness, attribution hygiene, memory notes, and clear next actions. Use at the end of a feature/bugfix/reference-integration branch before PR, merge, handoff, or cleanup. Branch name, diff summary, spec/plan, validation output, review state, attribution obligations, memory/follow-up needs, and cleanup constraints. A branch-finish report or PR-ready summary with clean status, validation evidence, review state, attribution state, and follow-ups.

187 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use chinese-code-review, chinese-commit-conventions and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • Leodorareluctant259Skill

    chinese-code-review

    中文代码审查规范——在保持专业严谨的同时，用符合国内团队文化的方式给出有效反馈

    Also in 8 projects that use this

  • Leodorareluctant259Skill

    chinese-commit-conventions

    中文 Git 提交规范 — 适配国内团队的 commit message 规范和 changelog 自动化

    Also in 8 projects that use this

  • obraSkill

    diagnosing-superpowers

    Use when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.

    Also in 20 projects that use this

  • kntismSkill

    condition-based-waiting

    Use when tests have race conditions, timing dependencies, or inconsistent pass/fail behavior - replaces arbitrary timeouts with condition polling to wait for actual state changes, eliminating flaky tests from timing guesses

    Also in 3 projects that use this

  • MicrosoftSkill

    testing-anti-patterns

    Use when writing or changing tests, adding mocks, or tempted to add test-only methods to production code - prevents testing mock behavior, production pollution with test-only methods, and mocking without understanding dependencies

    Also in 4 projects that use this

  • MicrosoftSkill

    root-cause-tracing

    Use when errors occur deep in execution and you need to trace back to find the original trigger - systematically traces bugs backward through call stack, adding instrumentation when needed, to identify source of invalid data or incorrect behavior

    Also in 5 projects that use this

  • +3 more from Leodorareluctant259

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 3 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 173 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

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

    Use at the end of a feature/bugfix/reference-integration branch before PR, merge, handoff, or cleanup.

    line 20
  2. Distinctive:

    Run or summarize final validation and note exact failures/limitations.

    line 30
  3. Distinctive:

    Ensure review feedback is handled or explicitly deferred.

    line 31
  4. Distinctive:

    Update memory, changelog, attribution, or reference notes when the work created durable knowledge.

    line 32

“Common” is measured: kept by at least 6 in 10 of the 173 edited versions of this file we could read. “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

Skill: Finishing a Development Branch

Purpose

Close a branch cleanly with verified status, review readiness, attribution hygiene, memory notes, and clear next actions.

When to use

Use at the end of a feature/bugfix/reference-integration branch before PR, merge, handoff, or cleanup.

Inputs

Branch name, diff summary, spec/plan, validation output, review state, attribution obligations, memory/follow-up needs, and cleanup constraints.

Workflow

  1. Inspect git status, branch name, and recent commits.
  2. Confirm the diff matches the accepted scope and no generated or upstream clone artifacts are staged accidentally.
  3. Run or summarize final validation and note exact failures/limitations.
  4. Ensure review feedback is handled or explicitly deferred.
  5. Update memory, changelog, attribution, or reference notes when the work created durable knowledge.
  6. Prepare a final handoff or PR summary with changed files, checks, risks, assumptions, and cleanup tasks.

Outputs

A branch-finish report or PR-ready summary with clean status, validation evidence, review state, attribution state, and follow-ups.

Failure modes

  • Finishing with unreviewed unrelated changes.
  • Claiming completion while validation is unknown.
  • Forgetting attribution or reference changelog updates.
  • Leaving branch/worktree cleanup ambiguous.

Verification checklist

  • Working tree and branch status are known.
  • Diff matches scope.
  • Final checks are reported honestly.
  • Review, attribution, and memory obligations are addressed.

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