gate-policies
Skill6 starsChanged 25 days agoNo licenceView on GitHub
The web team's ticket labels and the gate policies they activate — ff-required / ff-none, rollout-plan, qa-dev / qa-stakeholder, design-needed / design-none and the "-ask" labels — which output artifact each label is derived from, when a change needs a flag, the dangerous label combinations, each policy by gate (deployment, validation, delivery) with who passes it and when an agent may, and the proposed auto-merge policies (Dependabot, docs, tests, dashboards, revert) with their limits. Use when labeling a ticket in refinement, when checking whether the labels match the spec, or when someone asks "which label do I use?", "does this need a flag?" or "can this merge on its own?". Invoke as /gate-policies [TICKET-KEY].
In this repository18 other files it gives its agents.
- acceptance-criteriaSkill
- app-designSkill
- ci-cdSkill
- credentialsSkill
- definition-of-readySkill
- feature-flagsSkill
- gitflowSkill
- grafana-dashboardsSkill
- kubectlSkill
- observabilitySkill
- pull-requestSkill
- refinement-contextSkill
- rollout-planSkill
- secret-or-settingSkill
- skill-designSkill
- task-trackerSkill
- test-appsSkill
- ticket-lifecycleSkill
The file
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.