agentleFS
Sign inStart free
gregwebsgregwebs/skills-sdlc/skills/wrap-up/SKILL.md

wrap-up

Skill20 starsChanged 44 days agoMITView on GitHub

After implementing, commit and finish your work

61 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use refine, doctor 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.
  • AlexPEClubSkill

    refine

    Always use when the user wants to discuss an exsiting feature or specification. Open an existing feature spec to improve, extend, or fundamentally challenge it. Pass the feature ID as argument (e.g. /refine PROJ-2).

    Also in 3 projects that use this

  • 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

  • MicrosoftSkill

    sync

    Sync the current session branch with its upstream branch, or publish the current session branch to a remote. Use when the user asks to sync a branch, pull latest changes, rebase onto upstream, push current branch, publish branch, or set upstream.

    Also in 3 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

7 rules. 0 are common, 6 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 56 edited versions we read keep these.

  • 6

    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
  • could be automatic: a setting could enforce it
  1. Distinctive:

    Ensure you are on a branch at the apropriate location.

    line 6
  2. Distinctive:

    Do a fetch of the origin repo to see if there have been updates.

    line 8
  3. Very specific:

    Use the /document-changes skill to help record your changes in commit messages and pull requests.

    line 12
  4. Distinctive:

    Do the following if your instructions authorize/direct it and the capability is available.

    line 14
  5. Distinctive:

    When fixing CI failures, if the PR has not yet been reviewed, continue to squash commits together and force push the branch.

    line 19
  6. Distinctive:

    If the PR has been reviewed, generate a single squash commit message to be used when the PR is merged.

    line 20
  7. Distinctive:

    Ask the user whether to create tickets/issues for out of scope work brought up:

    line 22

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

Ensure you are on a branch at the apropriate location. This is usually the tip of main. Do a fetch of the origin repo to see if there have been updates.

Commit your work. Squash your commits down to a concise history useful for future viewers of history (usually just 1 commit). Use the /document-changes skill to help record your changes in commit messages and pull requests.

Do the following if your instructions authorize/direct it and the capability is available.

  • Generate a /pull-request
  • Watch for CI success

For a multi-commit Pull Request, generate a combined commit message that can be used in a squash merge. When fixing CI failures, if the PR has not yet been reviewed, continue to squash commits together and force push the branch. If the PR has been reviewed, generate a single squash commit message to be used when the PR is merged.

Ask the user whether to create tickets/issues for out of scope work brought up:

  • Unrelated defects
  • Small related features/enhancements
  • Improving the software development process- altering documentation or skills to streamline agent usage

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