agentleFS
Sign inStart free
timursafiullintimursafiullin/aod/skills/close/SKILL.md

close

Skill0 starsChanged 29 days agoApache-2.0View on GitHub

Close an accepted AOD task - squash merge the implementer branch into the base branch with trailers, the report, the ledger and the journal entry in one commit, then reset the worktree slot. Use after /aod:verify gives ACCEPT.

27 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use open, reconcile and 7 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.
  • BlockSkill

    open

    Open markdown documents in Penpal for collaborative review. Use when you want a human to review a document, plan, or research artifact.

    Also in 5 projects that use this

  • howellsSkill

    reconcile

    Audit a project against current plugin conventions and offer to update structure.

    Also in 3 projects that use this

  • Microsoft AzureSkill

    validate

    Run the full CI validation workflow locally before submitting a PR. Use this as a final check to ensure all Azure DevOps CI pipeline steps will pass.

    Also in 4 projects that use this

  • AnthropicSkill

    start

    Set up your bio-research environment and explore available tools. Use when first getting oriented with the plugin, checking which literature, drug-discovery, or visualization MCP servers are connected, or surveying available analysis skills before starting a new project.

    Also in 6 projects that use this

  • BlockSkill

    plan

    Draft a TDD, PRD, or lightweight plan in the conversation without committing it.

    Also in 8 projects that use this

  • OpenAISkill

    bootstrap

    Project bootstrapping orchestrator for repos that depend on Vercel-linked resources (databases, auth, and managed integrations). Use when setting up or repairing a repository so linking, environment provisioning, env pulls, and first-run db/dev commands happen in the correct safe order.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 22 edited versions we read keep these.

  • 0

    Distinctive

    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:

    Write the journal line first, in today's entry .agents/journal/YYYY-MM-DD-<slug>.md (create it from .agents/journal/README.md if missing): …

    line 10
  2. Very specific:

    After every 3-5 closed tasks, or at the end of a milestone, suggest /aod:retro.

    line 21

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

Close T-xxxx

CLI: aod means node "${CLAUDE_PLUGIN_ROOT}/scripts/aod.mjs".

  1. Write the journal line first, in today's entry .agents/journal/YYYY-MM-DD-<slug>.md (create it from .agents/journal/README.md if missing): what was merged, rounds, reviewer verdict, backlog items from minor findings. Leave it uncommitted.
  2. The main checkout must be on the base branch with no uncommitted changes except the ledger (.agents/tasks/index.*) and that journal file.
  3. Merge (refuses if gates did not pass, the branch or slot changed since, or there are conflicts): aod merge T-xxxx --reviewed-by "<reviewer, e.g. aod:reviewer (sonnet, fresh context)>" --journal .agents/journal/<file>.md --attention <minutes of the user's attention, if known> One squash commit then holds the code, the packet, the acceptance tests, the report, the ledger and the journal. Add --prune to delete task/T-xxxx and codex/T-xxxx afterwards.
  4. Confirm the base branch is green by running the project's test command.
  5. Pushing is the user's call; do not push unless asked.
  6. After every 3-5 closed tasks, or at the end of a milestone, suggest /aod:retro.

Ledger rule: .agents/tasks/index.json and index.md may stay uncommitted on the base branch while you work. They are committed by aod merge (with the task) or by aod session end --commit, whichever comes first, and never on a task branch.

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