release-readiness
Skill11 starsChanged 3 months agoNo licenceView on GitHub
Use on Desktop when deciding whether a branch, build, package, or product increment is ready to release or hand off.
We split this skill into the rules it gives an agent
3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 44 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
“Common” is measured: kept by at least 6 in 10 of the 44 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.
Other versions45 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 45
- dotnet/maui★ 23ksame name
- pulsejet/memories★ 3.9ksame name
- AIEraDev/Clypra★ 3.3ksame name
- jordanhubbard/nanolang★ 628same name
- petrkindlmann/qa-skills★ 209same name
- colasama/MahoShojo-Generator★ 167same name
- MRCalderon3D/everything-game-dev-code★ 91same name
- Azure/odinforazurelocal★ 20same name
- jpantsjoha/ai-native-developer-experience★ 13same name
- NotHarshhaa/devops-skills★ 8same name
35 more not listed
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.
Used alongsideProjects with it also use dependency-cve-sweep, fleet-standard-adoption and 6 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
berntpoppSkilldependency-cve-sweep
Use when handling Dependabot PRs, CodeQL/Trivy alerts, or doing a routine dependency/CVE sweep for this repo.
Also in 12 projects that use this
- berntpoppSkill
fleet-standard-adoption
Use when bringing this repo into compliance with a GeneFoundry fleet standard (tool-naming, response-envelope, container-hardening, versioning, MCP transport, or logging) or closing its tracking issue.
Also in 12 projects that use this
IgorGanapolskySkillci-failure-triage
Triage a CI / PR check failure by READING the failure body before forming any hypothesis. Triggered whenever a required check is red, a PR is BLOCKED, a merge won't land, or you're about to call a failure "transient", "flaky", "stale", or "orphaned". Prevents dismissing a real failure (e.g. real CodeQL security alerts) as noise.
Also in 13 projects that use this
VersoXBTSkillcode-quality-review
Perform structured code reviews enforcing quality standards, naming conventions, architecture patterns, and team agreements. Use when the user says 'review this code', 'code review', 'check quality', 'review my PR', 'what's wrong with this', 'improve this code', 'review before merge', 'peer review', or 'audit this'. Also triggers on 'code quality', 'review standards', 'enforce conventions', 'tech debt check', 'lint review', or when user completes a significant code change.
Also in 12 projects that use this
ffsshhttiikkSkillunit-testing
Unit testing best practices and patterns
Also in 3 projects that use this
jarosser06Skilltest-strategy
Plans pytest test strategies for Drift's 90%+ coverage requirement using coverage analysis, edge case identification, and test suite design. Use when determining what tests to write, analyzing coverage gaps, or planning test strategies.
Also in 4 projects that use this
- +2 more from berntpopp
In this repository36 other files it gives its agents.
- AGENTS.mdAGENTS.md
- architecture-decision-recordSkill
- cli-designSkill
- code-reviewSkill
- code-tourSkill
- context-mappingSkill
- credit-risk-analysisSkill
- daily-focusSkill
- data-analysisSkill
- dependency-update-planningSkill
- diagrammingSkill
- documentation-writingSkill
- email-draftingSkill
- evidence-mappingSkill
- file-organizationSkill
- frontend-designSkill
- git-deliverySkill
- github-actions-hardeningSkill
- github-release-planningSkill
- implementation-planningSkill
- incident-postmortemSkill
- meeting-minutesSkill
- performance-review-writingSkill
- privacy-compliance-reviewSkill
- professional-postSkill
- project-onboardingSkill
- requirements-discoverySkill
- security-reviewSkill
- skill-creatorSkill
- sql-optimizationSkill
- sql-reviewSkill
- systematic-debuggingSkill
- system-command-planningSkill
- technical-spikeSkill
- test-driven-developmentSkill
- verification-before-completionSkill
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.