repository-delivery-gate
Skill1 starsChanged 3 months agoApache-2.0View on GitHub
Decide whether a repository change is ready for review, merge, release, deployment, or handoff using evidence proportionate to risk.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- sodejm/copilot-operation-plugin-for-securityword for word, first seen Oct 23, 2026
Other versions1 project uses a version of this.
Word for word · 1
- sodejm/copilot-operation-plugin-for-security★ 2100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
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 repository28 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- agent-workboardSkill
- clear-writingSkill
- documentation-impactSkill
- github-state-auditSkill
- gitignore-auditSkill
- milestone-deliverySkill
- repository-checkSkill
- repository-orientationSkill
- resumable-worktree-runSkill
- security-reviewSkill
- session-usage-auditSkill
- template-project-creatorSkill
- agent-workboardSkill
- clear-writingSkill
- documentation-impactSkill
- github-state-auditSkill
- gitignore-auditSkill
- milestone-deliverySkill
- repository-checkSkill
- repository-delivery-gateSkill
- repository-orientationSkill
- resumable-worktree-runSkill
- security-reviewSkill
- session-usage-auditSkill
- template-project-creatorSkill
The file
Files
Repository delivery gate
Evaluate the requested transition, not an assumed one.
- Scope: acceptance criteria are met and unrelated work is excluded.
- Artifact: exact diff, branch, commit, generated files, and migrations are known.
- Quality: focused checks and
make checkpass in the current checkout. - Documentation: user, contributor, architecture, operations, and security impact is updated or a no-impact rationale is recorded.
- Security: secrets, dependencies, permissions, untrusted input, and abuse cases receive review proportionate to risk.
- Operations: rollout, compatibility, data migration, observability, and rollback are addressed when applicable.
- Hosted state: PR reviews, required checks, mergeability, release, and deployment are refreshed from authoritative sources when relevant.
Return one outcome: ready, ready with stated residual risk, or not ready with a specific blocker. Keep local commit, pushed branch, open PR, merged PR, release, and deployment states distinct. Do not perform the transition unless authorized.
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.

