agentleFS
haqalizhaqaliz/assay/.claude/skills/assay-end/SKILL.md

assay-end

Skill0 starsChanged 3 days agoApache-2.0View on GitHub

Use when finishing local work on an Assay unit of work after the PR is merged and you also need a completion report in Projects Brain. Triggers on "assay-end", "ae", "ae bug 12", "ae feat skill-ingest", "end full".

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 1 is distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

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

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

    REQUIRED SUB-SKILL: Use assay-end-fast for the cleanup pipeline.

    line 18
  2. Very specific:

    Run its Phase 0 → Phase 2 exactly as written.

    line 20
  3. Distinctive:

    Phase 3 (release) is deferred: Only proceed to the report once cleanup verification passes.

    line 21
  4. Very specific:

    REQUIRED SUB-SKILL: Use assay-report with the unit-of-work id and type.

    line 26

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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

Assay End (Full Track)

Overview

Same cleanup as assay-end-fast, plus a completion report at the end via assay-report.

Invocation: ae <type> <id> — e.g. ae bug 12, ae feat skill-ingest.

Pipeline

REQUIRED SUB-SKILL: Use assay-end-fast for the cleanup pipeline.

Run its Phase 0 → Phase 2 exactly as written. Assay's base branch is master. Phase 3 (release) is deferred. Only proceed to the report once cleanup verification passes.

Phase 4 — Completion report

REQUIRED SUB-SKILL: Use assay-report with the unit-of-work id and type.

ae argassay-report arg
bugbug
task / choretask
feat / featurefeature

Phase 5 — Comment on the issue (optional)

Same approach as assay-end-fast Phase 4. Skip if there's no reachable issue.

Common mistakes

MistakeFix
Running the report before cleanupPhases 0–2 first
Passing the wrong type to assay-reportApply the mapping table
Cleaning up against masterAssay's base branch is master
Trying to cut a release during endDeferred

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.