signoff
Skill4 starsChanged 41 days agoApache-2.0View on GitHub
Summarise an Aevum block that is ready for sign-off and record the user's approve or reject decision.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- RAMA-L7/vlsi-pd-staff-engineertheir own version, first seen Nov 16, 2026
- mmnto-ai/totemtheir own version, first seen Sep 25, 2026
- LuckyCody/signofftheir own version, first seen Jun 10, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- mmnto-ai/totem★ 18same name
- RAMA-L7/vlsi-pd-staff-engineer★ 3same name
- LuckyCody/signoff★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
1
Distinctive
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
- Very specific: line 21
If the arguments say approve or reject, write exactly one of logs/blocks/<BLOCK_ID>/signoff/SIGNED.md or REJECTED.md with the founder's …
- Distinctive: line 27
After an approval, give the human-only next step as commands for the user to run: fast-forward main to the integration branch.
“Common” is measured: kept by at least 6 in 10 of the 3 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.
Files
Sign-off is the founder's decision. You prepare the evidence and write the file only when the user's own message carries the decision.
- From
logs/blocks/<BLOCK_ID>/progress.jsonl, find the latestblock_ready_for_signoffand itsintegration_sha. Confirmgit rev-parse block/<BLOCK_ID>/integrationmatches. If there is no such event, say what state the block is in and stop. - Summarise in a few lines: clusters closed, the block-close gate
verdicts (
logs/gates/gate1-delta.json,gate2.json,gate3a.json,gate3b.json), fix-loop iterations, open gate3b warnings, andgit diff --stat <base_sha>..<integration_sha>. - If the arguments say
approveorreject, write exactly one oflogs/blocks/<BLOCK_ID>/signoff/SIGNED.mdorREJECTED.mdwith the founder's name (ask; suggestgit config user.name), the UTC date, the integration SHA, and eitherapprovedon its own line or the reason. Without a decision in the arguments, stop after the summary. - After an approval, give the human-only next step as commands for the
user to run: fast-forward
mainto the integration branch. Never run it yourself, and never push.
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.

