project-release
Skill0 starsChanged 41 days agoApache-2.0View on GitHub
Prepare stack-specific CI/CD and assess current-source local E2E and actual hosted CI/review evidence before authorized delivery.
7 other projects use a version of this.
Adopted by
Most recently taken up by
- ericwang200608-beep/LANYANT-Skillstheir own version, first seen Nov 8, 2026
- juanitourquiza/shipframetheir own version, first seen Oct 23, 2026
- DavidLam-oss/obsidian-wechat-convertertheir own version, first seen Oct 8, 2026
- kisev/skillstheir own version, first seen Sep 30, 2026
- salitaba/maven-decoder-mcptheir own version, first seen Sep 8, 2026
- breakstring/cfKanbantheir own version, first seen Sep 1, 2026
Other versions7 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 7
- DavidLam-oss/obsidian-wechat-converter★ 358same name
- swimmwatch/cloakbrowser-mcp★ 172same name
- breakstring/cfKanban★ 24same name
- salitaba/maven-decoder-mcp★ 20same name
- juanitourquiza/shipframe★ 4same name
- ericwang200608-beep/LANYANT-Skills★ 2same name
- kisev/skills★ 2same 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 repository14 other files it gives its agents.
- AGENTS.mdAGENTS.md
- business-operationsSkill
- capability-managerSkill
- decision-routingSkill
- global-orchestratorSkill
- integration-builderSkill
- plugin-safety-reviewSkill
- project-designSkill
- project-discoverySkill
- project-documentationSkill
- project-evidence-reviewSkill
- project-knowledgeSkill
- project-qaSkill
- project-securitySkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 4 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 5 edited versions we read keep these.
4
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
- Distinctive: line 8
Use the actual confirmed language/runtime, lockfile, test commands, repo/branch and deployment target.
- Distinctive: line 10
Use verified full action/reusable-workflow SHAs, minimal token permissions, safe untrusted input and appropriately isolated runners.
- Very specific: line 11
Use an explicit final CI gate that rejects absent/failed/cancelled/neutral/skipped required jobs.
- Distinctive: line 12
Before merge/deploy, verify current head, actual checks, independent review, branch/environment rules, residual blockers and rollback.
- Distinctive: line 13
No push, PR creation, remote settings change, merge, deployment or external messages without authority for the action/target.
“Common” is measured: kept by at least 6 in 10 of the 5 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
Project Release
Use the actual confirmed language/runtime, lockfile, test commands, repo/branch and deployment target. Preserve existing workflows/rules; do not generate a universal fake CI pipeline. Require current-source local checks and actual E2E acceptance journeys before application/feature code pushes. Missing/failed/skipped required checks block the push. Source changes invalidate affected evidence. Use verified full action/reusable-workflow SHAs, minimal token permissions, safe untrusted input and appropriately isolated runners. Never execute untrusted PR code with secrets in privileged contexts. Use an explicit final CI gate that rejects absent/failed/cancelled/neutral/skipped required jobs. Hosted CI is checked after the authorized push on the actual relevant head/test-merge/merge-group revision; local emulation is not hosted evidence. Before merge/deploy, verify current head, actual checks, independent review, branch/environment rules, residual blockers and rollback. A YAML file does not establish remote branch protection. No push, PR creation, remote settings change, merge, deployment or external messages without authority for the action/target. Preserve authorization already given. Keep current delivery instructions under docs/.
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.