engineering-bar
Skill0 starsChanged 16 days agoMITView on GitHub
Shared engineering quality bar for any change — correctness, hygiene, structure, failure, data, security, performance guards, operability, and UI. Use when another skill says to apply the engineering bar, when asked if work meets engineering standards, or before calling a change done.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- rpraharaj/ai-engineertheir own version, first seen Nov 1, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- rpraharaj/ai-engineer★ 1same 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 repository66 other files it gives its agents.
- AGENTS.mdAGENTS.md
- a11y-passSkill
- assess-changeSkill
- build-regression-packSkill
- charter-exploratorySkill
- classify-dataSkill
- commitSkill
- cut-releaseSkill
- data-changeSkill
- debugSkill
- design-experimentSkill
- diff-environmentsSkill
- draft-steercoSkill
- explain-codeSkill
- explore-codebaseSkill
- fix-ciSkill
- handoffSkill
- implement-changeSkill
- incident-triageSkill
- lean-reviewSkill
- map-dependenciesSkill
- map-design-handoffSkill
- map-processSkill
- open-prSkill
- performanceSkill
- plan-data-migrationSkill
- plan-incrementSkill
- plan-rollbackSkill
- plan-uatSkill
- prioritize-backlogSkill
- production-passSkill
- ready-to-mergeSkill
- record-decisionSkill
- refactor-safelySkill
- revert-changeSkill
- review-architectureSkill
- review-changeSkill
- review-pipelineSkill
- security-passSkill
- shape-workSkill
- ship-notesSkill
- spec-analyticsSkill
- spec-observabilitySkill
- start-projectSkill
- synthesize-discoverySkill
- triage-blockersSkill
- triage-defectSkill
- update-raidSkill
- verify-uiSkill
- write-api-examplesSkill
- write-architectureSkill
- write-designSkill
- write-dev-tasksSkill
- write-docsSkill
- write-integration-contractSkill
- write-nfrSkill
- write-opportunitySkill
- write-prdSkill
- write-requirementsSkill
- write-runbookSkill
- The first 60 shown.
The file
Files
Engineering bar
Apply this to the current diff, not the whole product. Other skills load this file (sibling ../engineering-bar/SKILL.md). The detailed checks live in references/bar.md — open that file when you apply the bar.
Is this the right skill?
| Signal | Do this instead |
| Full merge gate | ready-to-merge (it applies this bar) |
| Threat model of the diff | security-pass |
| Delete-list only | lean-review |
Required inputs
- The current diff
AGENTS.mdif present (repo commands win)
Human decisions (do not invent)
- Waiving a fail
Procedure
- Read references/bar.md.
- Walk each section on this diff. Mark pass, fail, or n/a.
- Fix fails or get an explicit user waiver. Do not invent extra standards this repo does not use.
Output
- Path: reply (fails and waivers only)
- Template:
references/bar.md
Quality bar
- Secret files section applied
- Fails have a file or an explicit waiver
- Silence on a section means pass or n/a — say which
Done
Report only fails and waivers, then the list of checks that ran.
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.