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".
In this repository10 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- assay-begin-fastSkill
- assay-beginSkill
- assay-end-fastSkill
- assay-nextSkill
- assay-reportSkill
- assay-worktreesSkill
- prd-generatorSkill
- prd-interviewSkill
- tech-planSkill
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
- Very specific: line 18
REQUIRED SUB-SKILL: Use assay-end-fast for the cleanup pipeline.
- Very specific: line 20
Run its Phase 0 → Phase 2 exactly as written.
- Distinctive: line 21
Phase 3 (release) is deferred: Only proceed to the report once cleanup verification passes.
- Very specific: line 26
REQUIRED SUB-SKILL: Use assay-report with the unit-of-work id and type.
≈ “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.
Files
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 arg | assay-report arg |
bug | bug |
task / chore | task |
feat / feature | feature |
Phase 5 — Comment on the issue (optional)
Same approach as assay-end-fast Phase 4. Skip if there's no reachable issue.
Common mistakes
| Mistake | Fix |
| Running the report before cleanup | Phases 0–2 first |
Passing the wrong type to assay-report | Apply the mapping table |
Cleaning up against master | Assay's base branch is master |
| Trying to cut a release during end | Deferred |
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
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.

