agentleFS
GavinGreenwoodGavinGreenwood/agentic-workflow-template/.agents/skills/wrap-up/SKILL.md

wrap-up

Skill5 starsChanged 44 days agoMITView on GitHub

User-invoked only. Switch to main and pull latest, then delete the finished feature branch. Does not merge anything — use `pr` for that. Checks for uncommitted changes and whether the branch was pushed before deleting.

62 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use doctor, orchestration and 8 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.
  • MicrosoftSkill

    doctor

    Diagnose an Amplifier CLI environment through the CLI doctor agent. USE WHEN a user requests CLI runtime, settings or missing-capability inspection. DO NOT USE for project bugs or other hosts.

    Also in 4 projects that use this

  • austintgriffithSkill

    orchestration

    Use when a Scaffold-ETH 2 build leaves localhost: planning the launch order, deploying and verifying contracts on a live network, standing up a fork of a real chain to rehearse a deploy, or fixing a contract bug that is already onchain. Not for running the app or a demo against that fork (`/frontend-playbook`).

    Also in 3 projects that use this

  • SentrySkill

    spec

    Produce a verified spec — problem, desired outcome, and acceptance criteria — before building. Use when given a GitHub/Linear issue link, when starting from a fuzzy in-conversation idea, or asked to "figure out what to do" / "scope this" / "what should I build" — whenever the *what* isn't yet pinned down. Grills the ambiguities, checks the premise against the code, and produces acceptance criteria you sign off on — then hands to design-first.

    Also in 5 projects that use this

  • nicolasestremSkill

    brainstorm

    Structured idea generation and solution exploration with systematic analysis.

    Also in 5 projects that use this

  • OpenAISkill

    security-scan

    Use for a standard, single-pass security audit of an entire repository or a scoped path, package, folder, or submodule with no diff to review. This is the default repository scan. Do not use for PR, commit, branch, or working-tree diffs, or for deep, multi-pass scans.

    Also in 3 projects that use this

  • seikaikyoSkill

    interview-me

    需求不明時的意圖萃取訪談:一次一題、每題附上自己的猜測、聽出「真正想要 vs 覺得應該要」,直到能預測使用者反應(約 95% 信心)才動工。適用:需求缺少對象 / 動機 / 成功標準 / 約束,或使用者點名「訪談我」「先確認一下」「我們確定嗎」。明確自足的指示、純資訊查詢、機械性操作不適用。

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

11 rules. 0 are common, 7 are distinctive, and 4 are very specific to this project.

  • 0

    Common

    Most of the 57 edited versions we read keep these.

  • 7

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run this before anything else, and do not act on any later step until you have its output.

    line 10
  2. Distinctive:

    Follow this decision tree exactly:

    line 20
  3. Distinctive:

    If there are any uncommitted changes (staged or unstaged), stop immediately and tell the user:

    line 26
  4. Distinctive:

    Do not proceed further.

    line 30
  5. Distinctive:

    If already on main, just run git pull and report that main is up to date.

    line 38
  6. Very specific:

    If a tracking branch exists: git log @{u}..HEAD --oneline --max-count=1 — check if there are commits not yet pushed to upstream.

    line 48
  7. Very specific:

    Delete the local branch: git branch -d <branch>

    line 54
  8. Very specific:

    Ask the user: "Branch <branch> has unpushed commits.

    line 66
  9. Very specific:

    If user says delete: switch to main, pull, then git branch -D <branch> and notify.

    line 67
  10. Distinctive:

    If user says keep: switch to main, pull, and leave the branch in place.

    line 68
  11. Distinctive:

    Always end with a clear one-line status: what branch you're on now, whether you deleted anything, and whether pull succeeded.

    line 74

“Common” is measured: kept by at least 6 in 10 of the 57 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

Step 0 — Context (required first)

Run this before anything else, and do not act on any later step until you have its output. If a probe fails, stop and tell the user. Never assume these values.

echo "Current branch: $(git branch --show-current)"
echo "Git status (uncommitted changes):"; git status --porcelain
echo "Branches and their remote tracking status:"; git branch -v

Your Task

Follow this decision tree exactly:

Step 1 — Check for uncommitted changes

Run: git status --porcelain

If there are any uncommitted changes (staged or unstaged), stop immediately and tell the user:

"You have uncommitted changes on <branch>. Please commit, stash, or discard them before switching to main."

Do not proceed further.


Step 2 — Check if already on main

Run: git branch --show-current

If already on main, just run git pull and report that main is up to date. Done.


Step 3 — Feature branch: check for unique commits and remote tracking

Run these commands:

  • git log main..HEAD --oneline --max-count=1 — check if the branch has any commits that aren't on main.
  • git rev-parse --abbrev-ref --symbolic-full-name @{u} 2>/dev/null — check if a remote tracking branch exists.
  • If a tracking branch exists: git log @{u}..HEAD --oneline --max-count=1 — check if there are commits not yet pushed to upstream.

Branch has NO unique commits (no commits ahead of main, regardless of whether it was pushed):

  • Switch to main: git checkout main
  • Pull latest: git pull
  • Delete the local branch: git branch -d <branch>
  • Notify the user: "Switched to main, pulled latest, and deleted <branch> (no unique commits)."

Branch has been pushed (has commits ahead of main AND remote tracking branch exists AND no commits ahead of upstream):

  • Switch to main: git checkout main
  • Pull latest: git pull
  • Delete the local branch: git branch -d <branch>
  • Notify the user: "Switched to main, pulled latest, and deleted <branch> (was pushed to remote)."

Branch has unpushed commits (has commits ahead of main AND either no remote tracking branch OR commits ahead of upstream):

  • Ask the user: "Branch <branch> has unpushed commits. Delete it anyway, or keep it?"
  • If user says delete: switch to main, pull, then git branch -D <branch> and notify.
  • If user says keep: switch to main, pull, and leave the branch in place.

Summary output

Always end with a clear one-line status: what branch you're on now, whether you deleted anything, and whether pull succeeded.

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.