agentleFS
Sign inStart free
Arch1eSUNArch1eSUN/Arcgentic/skills/close-round/SKILL.md

close-round

Skill286 starsChanged 5 months agoMITView on GitHub

Use only after an arcgentic round has an external audit PASS and state.yaml is in passed. Anchors the verdict, runs strict audit-check, transitions passed to closed, and records the last passed round without writing an external audit verdict.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 3 are distinctive, and 1 is 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.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Do not run before external audit PASS.

    line 38
  2. Distinctive:

    Do not write, edit, or replace the external audit verdict.

    line 39
  3. Very specific:

    Do not use close-round to resolve NEEDS_FIX or AUDIT_INCOMPLETE.

    line 40
  4. Distinctive:

    Do not perform release tagging, publishing, or next-round planning unless the user explicitly starts that separate orchestrator step.

    line 41

≈ “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

close-round

Closes an arcgentic round after external audit PASS. This is an orchestrator-owned closeout seam, not a developer or auditor task.

Preconditions

  1. .agentic-rounds/state.yaml has current_round.state: passed.
  2. current_round.audit_verdict.outcome is PASS.
  3. current_round.audit_verdict.commit is set to the audit commit.
  4. The verdict file exists and passes both:
    • arcgentic verdict-completeness <verdict.md>
    • arcgentic audit-check <verdict.md> --strict --strict-extended

Command

arcgentic close-round \
  --state-file .agentic-rounds/state.yaml \
  --verdict <docs/audits/round-verdict.md> \
  --audit-commit <audit-commit-sha>

Outputs

  • current_round.state becomes closed.
  • current_round.state_history gains a closed entry.
  • last_passed_round records round id, audit commit, verdict doc, and close time.
  • The command prints a next-round recommendation for the orchestrator.

Boundaries

  • Do not run before external audit PASS.
  • Do not write, edit, or replace the external audit verdict.
  • Do not use close-round to resolve NEEDS_FIX or AUDIT_INCOMPLETE.
  • Do not perform release tagging, publishing, or next-round planning unless the user explicitly starts that separate orchestrator step.

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