production-pass
Skill1 starsChanged 16 days agoMITView on GitHub
Check whether this change is safe to run in production — timeouts, retries and idempotency, visibility, rollback, and compatibility. Use when the change adds I/O, jobs, queues, webhooks, flags, or public contracts, when ready-to-merge dispatches it, or when the user asks if a change is production-safe.
1 other project uses a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- rpraharaj/ai-sdlcedited, first seen Nov 1, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 1
- rpraharaj/ai-sdlc★ 021% same
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 repository34 other files it gives its agents.
- AGENTS.mdAGENTS.md
- templates/AGENTS.mdAGENTS.md
- commitSkill
- cut-releaseSkill
- data-changeSkill
- debugSkill
- engineering-barSkill
- explain-codeSkill
- explore-codebaseSkill
- fix-ciSkill
- handoffSkill
- implement-changeSkill
- incident-triageSkill
- lean-reviewSkill
- open-prSkill
- performanceSkill
- ready-to-mergeSkill
- record-decisionSkill
- refactor-safelySkill
- resolve-conflictsSkill
- revert-changeSkill
- review-changeSkill
- security-passSkill
- shape-workSkill
- ship-notesSkill
- start-projectSkill
- upgrade-depsSkill
- verify-uiSkill
- write-architectureSkill
- write-designSkill
- write-dev-tasksSkill
- write-docsSkill
- write-prdSkill
- write-testsSkill
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 3 are distinctive, and 6 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 14
Read AGENTS.md if present.
- Very specific: line 18
Follow engineering-bar Shared procedures for scope and evidence, reusing the caller's recorded scope when provided.
- Very specific: line 27
Use the shared evidence statuses for each requirement.
- Distinctive: line 31
Every new outbound I/O uses a timeout or this repo's standard client (which already has one).
- Distinctive: line 35
If the change retries:
- Distinctive: line 40
If a webhook/job can be delivered twice, handling it twice must not corrupt state.
- Very specific: line 52
Write one sentence: how to undo this in production (revert-change, flip a flag already in the diff, restore the prior artifact).
- Very specific: line 62
Do not invent a migration here.
- Very specific: line 78
If the user asked to fix fails, use implement-change and keep the diff small.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
Production pass
Operability of this delta. Do not redesign the platform. Do not edit product code unless the user asked you to fix fails.
Read AGENTS.md if present. Load engineering-bar (paths in that skill) for Failure + Operability + Data; this skill is how to walk those on a shipping change.
Collect
Follow engineering-bar Shared procedures for scope and evidence, reusing the caller's recorded scope when provided. Note new or changed:
- Outbound I/O (HTTP, DB, disk, subprocess)
- Inbound async (queue consumer, cron, webhook)
- Public contracts (API, events, flags)
- State that can be half-applied
Checks
Use the shared evidence statuses for each requirement; missing evidence is unverified, and irrelevant checks are not applicable. Fails need file:line.
Timeouts
Every new outbound I/O uses a timeout or this repo's standard client (which already has one). Infinite waits are a fail.
Retries and idempotency
If the change retries:
- Bound + jitter, or the repo's retry helper
- Safe to repeat (idempotency key, upsert, or the handler is naturally idempotent)
If a webhook/job can be delivered twice, handling it twice must not corrupt state.
Backpressure and bounds
New lists, batches, and jobs have a limit. Unbounded while/fan-out on request or consume paths is a fail.
Visibility
A new failure mode is visible with whatever this repo already uses (structured log, metric, trace, error reporter). The record includes enough to debug (operation, id) and no secrets.
Rollback
Write one sentence: how to undo this in production (revert-change, flip a flag already in the diff, restore the prior artifact). If you cannot, fail unless the change is trivially reversible by revert alone.
Compatibility
Public request/response, event, or flag changes are backward compatible for current callers, or the user accepted a break.
- Additive fields require producer/consumer evidence: a new required request field, strict decoder, enum value, or changed default can still break callers. Check old callers against new producers and new callers against old producers during rollout.
- Rename/remove/change meaning: fail while any supported reader or writer relies on the old shape. A separate contract phase may pass with the deployment, backfill, consumer migration, and rollback evidence required by
data-change; do not reject it solely because it removes a field. - Flag default that instantly forces a new path with no undo: fail unless rollback is documented
Do not invent a migration here. Do not call data-change from this skill — report the compat fail and stop.
Output
## Production pass: pass | fail | unverified
- Timeouts:
- Retries / idempotency:
- Bounds:
- Visibility:
- Rollback: <one sentence>
- Compatibility:
- Fails: …If the user asked to fix fails, use implement-change and keep the diff small.
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.