automated-standards-enforcement
Skill4 starsChanged 10 months agoMITView on GitHub
Use when creating or modifying any repository to establish automated quality enforcement (linting, spelling, tests, SAST, security). Applies by default unless user explicitly refuses. Ensures clean build policy with minimal developer friction.
In this repository67 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- agents-onboardingSkill
- agent-workitem-automationSkill
- architecture-testingSkill
- aspire-integration-testingSkill
- best-practice-introductionSkill
- branching-strategy-and-conventionsSkill
- broken-windowSkill
- change-risk-rollbackSkill
- ci-cd-conformanceSkill
- component-boundary-ownershipSkill
- contract-consistency-validationSkill
- csharp-best-practicesSkill
- deployment-provenanceSkill
- documentation-as-codeSkill
- documentation-scaffoldSkill
- dotnet-bespoke-code-minimisationSkill
- dotnet-best-practicesSkill
- dotnet-domain-primitivesSkill
- dotnet-efcore-practicesSkill
- dotnet-healthchecksSkill
- dotnet-logging-serilogSkill
- dotnet-mapping-standardSkill
- dotnet-open-source-first-governanceSkill
- dotnet-source-generation-firstSkill
- dotnet-specification-patternSkill
- dotnet-testing-assertionsSkill
- environment-traceabilitySkill
- finishing-a-development-branch-iddSkill
- greenfield-baselineSkill
- impacted-scope-enforcementSkill
- incremental-change-impactSkill
- incremental-deploymentSkill
- innersource-governance-bootstrapSkill
- issue-driven-deliverySkill
- library-extraction-stabilisationSkill
- local-dev-experienceSkill
- markdown-authorSkill
- modern-csharp-coding-standardsSkill
- monorepo-orchestration-setupSkill
- observability-logging-baselineSkill
- pair-programmingSkill
- persona-switchingSkill
- process-skill-routerSkill
- quality-gate-enforcementSkill
- release-tagging-planSkill
- repo-best-practices-bootstrapSkill
- repository-foundation-bootstrapSkill
- requirements-gatheringSkill
- runtime-tooling-validationSkill
- safe-brownfield-refactorSkill
- scoped-colocationSkill
- security-processesSkill
- selective-build-testSkill
- semantic-version-impactSkill
- session-awareSkill
- skills-first-workflowSkill
- static-analysis-securitySkill
- structured-review-workflowSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 5 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
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 19
Use this matrix to select the appropriate bootstrapping skill:
- Distinctive: line 45
Only need repo security/compliance (use repo-best-practices-bootstrap)
- Distinctive: line 86
Run baseline to identify existing violations
- Very specific: line 87
Document in docs/known-issues.md with counts
- Distinctive: line 106
Use pre-built CI workflow templates for common platforms:
- Distinctive: line 119
Commit and verify workflow runs
≈ “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
Automated Standards Enforcement
Overview
P0 Foundational - Applies by default. Zero-warning clean builds. Baseline for brownfield.
REQUIRED: superpowers:verification-before-completion, superpowers:test-driven-development
Bootstrapping Skills Decision Matrix
Use this matrix to select the appropriate bootstrapping skill:
| If You Need To... | Use This Skill |
| Start a new project from scratch | greenfield-baseline |
| Add/audit quality tooling (linting, tests, SAST) | automated-standards-enforcement (this) |
| Add/audit repo security (branch protection, secret scanning) | repo-best-practices-bootstrap |
Skill Scope Comparison
| Aspect | greenfield-baseline | automated-standards-enforcement | repo-best-practices-bootstrap |
| Primary Focus | Project foundation | Quality tooling | Repo security/compliance |
| Project State | New (no existing code) | New or existing | New or existing |
| Outputs | Repo structure, CI/CD, docs | Linting, tests, SAST config | Branch rules, secrets config |
| Triggers | Entry point for new projects | Auto-triggered or standalone | Use after structure exists |
Invocation Context
- Greenfield projects: Auto-triggered by greenfield-baseline
- Brownfield projects: Invoke directly with brownfield approach
- Existing repos: Invoke directly for quality tooling audit/addition
Do NOT Use This Skill When
- Starting a brand new project (use greenfield-baseline, which triggers this skill)
- Only need repo security/compliance (use repo-best-practices-bootstrap)
- Quality tooling already exists and passes (no changes needed)
When to Use
- Creating/modifying repository
- Opt-out: User explicitly refuses
Core Workflow
- Announce skill (default for all repos)
- Identify: linting, spelling, tests, SAST, security
- Map to tools (Tool Comparison)
- Enforce: pre-commit hooks + CI
- Single-command local run (
npm run validate) - Document in README.md
- Clean build (zero warnings)
- Exceptions:
docs/known-issues.md - IDE integrations (IDE Integration)
- Brownfield: baseline, enforce on new code
Quick Reference
| Standard | Typical Tools | Enforcement |
| Linting | ESLint, Ruff, dotnet-format | Pre-commit + CI |
| Formatting | Prettier, Black | Pre-commit |
| Spelling | cspell | Pre-commit + CI |
| Tests | Jest, pytest, xUnit | CI (coverage gates) |
| Security | npm-audit, bandit, SAST | CI |
See Language Configs for ecosystem-specific setup.
Clean Build Policy
Zero warnings/errors required. Exceptions documented in docs/known-issues.md with
justification and remediation plan. See Git Hooks Setup
and CI Configuration for enforcement.
Brownfield Approach
- Run baseline to identify existing violations
- Document in
docs/known-issues.mdwith counts - Pre-commit: check modified files only
- CI: document baseline exceptions
- Incremental remediation over time
Red Flags - STOP
- "Can add linting later"
- "MVP doesn't need quality checks"
- "Too many violations to fix"
- "Hooks slow development"
- "Clean build too strict"
All mean: Apply brownfield approach or document explicit opt-out.
See Tool Comparison for selection guidance.
Reference CI Workflow Templates
Use pre-built CI workflow templates for common platforms:
| Platform | Template | Description |
| GitHub Actions | templates/github-lint-workflow.yml.template | Lint and format check |
| GitHub Actions | templates/github-security-workflow.yml.template | Security scanning |
| Azure DevOps | templates/azure-pipelines-lint.yml.template | Lint pipeline |
Using Templates
- Copy template to
.github/workflows/or pipeline directory - Replace
{LANGUAGE}with your primary language (node, dotnet, python) - Adjust tool commands to match your
package.json/Makefilescripts - Commit and verify workflow runs
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.