agentleFS
Sign inStart free
Hadi99KHadi99K/AGENT_SKILLS/wrap-phase/SKILL.md

wrap-phase

Skill3 starsChanged 26 days agoMITView on GitHub

Wraps up a development phase by cleaning AGENT_SYNC.md, summarizing work, and committing changes.

  • Commits and pushes

The file

We split this skill into the rules it gives an agent

10 rules. About 0 are common, 3 are distinctive, and 7 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 7

    Very specific

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

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

    Read AGENT_SYNC.md to understand the completed work.

    line 13
  2. Distinctive:

    Add a Phase Summary highlighting everything built and key technical fixes.

    line 14
  3. Distinctive:

    Update the Current Phase status to reflect completion.

    line 17
  4. Very specific:

    Use this when the user asks to "wrap up the phase", "wrap the phase", or "clean up AGENT_SYNC".

    line 22
  5. Distinctive:

    When invoked, execute the following steps without needing further confirmation:

    line 26
  6. Very specific:

    Analyze: Read AGENT_SYNC.md to grasp all recent sub-tasks and the handoff logs.

    line 27
  7. Very specific:

    Summarize: Create a clear ## 📖 Phase Summary: [Feature Name] section under the task board summarizing the accomplishments.

    line 28
  8. Very specific:

    Clean: Remove all [x] completed items from ## 📋 Session Task Board.

    line 29
  9. Very specific:

    Purge: Delete all older handoff messages under ## 💬 Handoff & Discussion Log EXCEPT for the single most recent one.

    line 30
  10. Very specific:

    Save & Commit: Write the updated file to disk, then use bash to run: git add AGENT_SYNC.md && git commit -m "docs: wrap phase - clean agent …

    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

What I do

  • Read AGENT_SYNC.md to understand the completed work.
  • Add a Phase Summary highlighting everything built and key technical fixes.
  • Clean the Handoff Log by deleting all older conversations and keeping ONLY the single most recent log.
  • Clear completed tasks from the Session Task Board.
  • Update the Current Phase status to reflect completion.
  • Stage, commit, and push the AGENT_SYNC.md file automatically.

When to use me

Use this when the user asks to "wrap up the phase", "wrap the phase", or "clean up AGENT_SYNC".

Execution Steps

When invoked, execute the following steps without needing further confirmation:

  1. Analyze: Read AGENT_SYNC.md to grasp all recent sub-tasks and the handoff logs.
  2. Summarize: Create a clear ## 📖 Phase Summary: [Feature Name] section under the task board summarizing the accomplishments.
  3. Clean: Remove all [x] completed items from ## 📋 Session Task Board. Replace them with a note like "All completed."
  4. Purge: Delete all older handoff messages under ## 💬 Handoff & Discussion Log EXCEPT for the single most recent one.
  5. Update State: Change the "Current Phase" in the state section to indicate completion (e.g., "[Phase Name] Complete ✅").
  6. Save & Commit: Write the updated file to disk, then use bash to run: git add AGENT_SYNC.md && git commit -m "docs: wrap phase - clean agent sync and add phase summary" && git push

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