environment-promotion-checker
Skill1 starsChanged 8 months agoMITView on GitHub
In this repository19 other files it gives its agents.
- deployment-risk-checkerSkill
- direct-vs-parallel-vs-phased-vs-pilot-selectorSkill
- go-live-readiness-reviewerSkill
- post-release-monitoring-planSkill
- release-cut-checkerSkill
- release-notes-writerSkill
- rollback-readiness-checkerSkill
- runbook-writerSkill
- uat-readiness-checkerSkill
- deployment-risk-checkerSkill
- direct-vs-parallel-vs-phased-vs-pilot-selectorSkill
- environment-promotion-checkerSkill
- go-live-readiness-reviewerSkill
- post-release-monitoring-planSkill
- release-cut-checkerSkill
- release-notes-writerSkill
- rollback-readiness-checkerSkill
- runbook-writerSkill
- uat-readiness-checkerSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 7 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
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 12
Check whether a build or release can be promoted cleanly across environments with consistent configuration, approvals, and evidence.
- Distinctive: line 53
Prefer executable artifacts over broad process prose.
- Distinctive: line 55
Keep the result usable in real runbooks, tickets, release docs, and repo workflows.
- Distinctive: line 58
Do not confuse “mostly tested” with release safety.
- Distinctive: line 59
Do not assume rollback works because it was written down once.
- Distinctive: line 60
Do not hide configuration drift or approval gaps.
- Distinctive: line 61
Do not optimize for release speed at the expense of operational recovery.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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
environment-promotion-checker
Purpose
Check whether a build or release can be promoted cleanly across environments with consistent configuration, approvals, and evidence.
Trigger this skill when
- A release, deployment, rollout, cutover, or environment promotion needs explicit operational review.
- You need deployment outputs that can feed engineering, operations, governance, or assessment work.
- The delivery plan risks confusion between readiness signals and actual release safety.
Expected inputs
- environment map
- promotion rules
- config differences
- test evidence
- approval status
Deliverables
- promotion assessment
- configuration drift findings
- approval/evidence gaps
- environment blockers
- next promotion action
Operating procedure
- Clarify the release context, deployment path, change window, and operational constraints.
- Separate what is proven, tested, approved, or rehearsed from what is merely assumed.
- Produce the skill-specific artifact or review output.
- Surface risks, dependencies, timing gaps, ownership gaps, and rollback concerns explicitly.
- Recommend the next best handoff instead of trying to solve the entire release lifecycle at once.
Quality gates
- The output is specific to the current release context.
- Uncertainty, dependencies, and decision blockers are visible.
- The result is usable by an engineering lead, release manager, SRE/ops owner, or assessment team.
- Operational safety, not only delivery speed, is reflected in the recommendation.
Handoff targets
- go-live-readiness-reviewer
- release-cut-checker
- deployment-risk-checker
Output style
- Be explicit about operational risk, timing, ownership, and reversibility.
- Prefer executable artifacts over broad process prose.
- Surface evidence gaps instead of inventing readiness.
- Keep the result usable in real runbooks, tickets, release docs, and repo workflows.
Failure modes to avoid
- Do not confuse “mostly tested” with release safety.
- Do not assume rollback works because it was written down once.
- Do not hide configuration drift or approval gaps.
- Do not optimize for release speed at the expense of operational recovery.
Minimum output skeleton
## Summary
## Findings
## Structured outputs
## Risks / blockers
## Open questions
## Recommended next skillDoes 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.

