system-audit
Skill1 starsChanged 7 months agoMITView on GitHub
Mandatory technical validation. Use when: finishing a feature, initializing a stack, or creating new instructions.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- chacosoldier/compabobtheir own version, first seen Oct 23, 2026
- cogpros/system-audittheir own version, first seen Jul 4, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- chacosoldier/compabob★ 34same name
- cogpros/system-audit★ 0same 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 repository3 other files it gives its agents.
- .github/copilot-instructions.mdCopilot instructions
- architecture-patternsSkill
- context-handoffSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
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 31
If any item is marked [ ], the task is NOT complete.
- Very specific: line 32
Use context7 to verify the latest standards if the stack is new.
≈ “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
SKILL: Quality & Integrity Audit
CONTEXT
This skill ensures that all generated code, configurations, and documentation adhere to professional engineering standards and the specific rules of this framework.
CHECKLIST
1. Architectural Integrity (@tech-lead)
- SRP: Does every new file have a single responsibility?
- DRY: Are there obvious duplications of logic or config?
- Coupling: Is the new feature properly decoupled from unrelated modules?
- Standard Compliance: Does the folder structure match the chosen stack's conventions?
2. Security (@appsec)
- No Secrets: Are there API keys, passwords, or PII in the code?
- Input Validation: Are all external inputs sanitized/validated?
- Permissions: Are file permissions and access levels appropriate?
3. Framework Alignment (@qa)
- TSON Integrity: Are the
.tsonfiles regenerated and valid? - Context Economy: Is the new feature adding unnecessary noise to the context?
- Discovery: Can the new files be found by
discovery.py?
PROTOCOL
- If any item is marked [ ], the task is NOT complete.
- Use
context7to verify the latest standards if the stack is new. - Produce an
ADR(Architecture Decision Record) if a significant standard was changed or established.
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.