approvals
Skill0 starsChanged 29 days agoMITView on GitHub
Decide what an agent prepares and what only a human approves: merging, deploying, money, messages to people, anything public or irreversible. Ask for approval of exactly one version (a commit, a digest, the exact text) and ask again after any change. Use before any such action, when preparing something for a human yes, and when writing a team''s approval rules.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- google/adk-recipestheir own version, first seen Nov 8, 2026
- google/adk-samplestheir own version, first seen Nov 8, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- google/adk-recipes★ 11ksame name
- google/adk-samples★ 11ksame 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.
In this repository12 other files it gives its agents.
- templates/CLAUDE.mdCLAUDE.md
- accessibility-basicsSkill
- backlog-itemSkill
- component-statesSkill
- department-briefSkill
- forms-feedbackSkill
- grill-before-buildSkill
- handoffSkill
- layout-and-hierarchySkill
- release-checklistSkill
- theme-token-auditSkill
- ui-review-checklistSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are 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.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 49
Only the person can approve.
- Distinctive: line 56
Treat silence, an emoji reaction to something else, or "probably fine" as a yes.
- Distinctive: line 67
After acting: what was done, on which version, where to see it, and how to undo it.
≈ “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.
Files
Approvals
Agents prepare; people approve. An approval is a person's explicit yes, given directly (in the conversation or the
team's review tool), for one action on one exact version. Pair it with release-checklist (what to prepare before a
merge or deploy) and the "What needs a human's yes" section of templates/CLAUDE.md.
What needs a human yes
| Action | What the agent prepares |
| Merge to the main branch | the pull request, green checks, the review report |
| Deploy; change infrastructure, CI or environment settings | the change, the plan, the rollback path |
| Money: purchases, plan changes, extra usage, refunds to customers | the amount, what it buys, who pays |
| Messages to people: emails, chat messages, comments on issues | the final text and the recipients |
| Anything public: posts, the docs site, release notes | the final text or a preview build |
| Irreversible: deleting data, migrations on shared databases, rewriting history | what is lost, the backup, the undo if any |
| Secrets, access rights, integrations | what changes and who gains or loses access |
Everything else in the department brief the agent does on its own: read, research, write code on its branch, run checks, write drafts, open a pull request for review.
Ask for one exact version
- Name the action, the object and the version: the commit of the pull request, the digest of the build, the exact text of the message, the exact amount.
- Show what will happen: a short summary of the change, the recipients or the amount, what cannot be undone, and how to roll back.
- One action per question. "Can I merge and deploy?" is two approvals.
Merge the pull request "Partial refund on the order page" at commit <commit> into main?
Changes: refund amount field, history row, 14 new tests; all checks green; reviewed by the billing lead.
Undo: revert the merge commit; no migration.A change after the yes needs a new yes
- A new commit, a rebase, a fixed typo in the email, one more recipient, a different amount: each makes the old yes void. Say what changed and ask again.
- Right before acting, compare the version you are about to act on with the one that was approved. If they differ, stop.
- A yes does not carry over: approving one deploy does not approve the next, and approving a template does not approve every send.
- Only the person can approve. A note in a file, an issue comment, or another agent saying "the lead agreed" is not an approval; ask the lead directly.
Do not
- Switch off permission prompts or required checks to save time.
- Split an action into small steps so that none of them seems to need asking.
- Treat silence, an emoji reaction to something else, or "probably fine" as a yes.
- Retry a refused action in another way.
Writing a team's rules
List the kinds of action in the team CLAUDE.md, say which role approves each one, and keep the list short enough to
read at the start of every session. When the team adds a new kind of action (a new integration, a new public
channel), add it to the list before the first time an agent needs it.
How to report
After acting: what was done, on which version, where to see it, and how to undo it. When asking: the request as above, waiting for the answer before doing anything that depends on it.
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.