Minimizing Ty Ecosystem Changes
astral-sh/ruff
A skill your agent uses when a user says "minimize this ty ecosystem change", "reproduce this ecosystem result", "investigate a primer difference", "investigate a mypyprimer difference"…
A skill your agent uses when preparing code for commit, PR, or merge - covers linting, type safety, bundle budgets, coverage thresholds, complexity limits, dependency audit, and dead code detection
Install Quality Enforcement
$ npx skills add NoobyGains/godmode --skill quality-enforcement -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install NoobyGains/godmode quality-enforcement --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/NoobyGains/godmode.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/quality-enforcement .claude/skills/quality-enforcement && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "quality-enforcement" agent skill from https://github.com/NoobyGains/godmode/tree/master/skills/quality-enforcement into .claude/skills/quality-enforcement/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "quality-enforcement", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/NoobyGains/godmode/tree/master/skills/quality-enforcementType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add NoobyGains/godmode --skill quality-enforcement -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install NoobyGains/godmode quality-enforcement --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/NoobyGains/godmode.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/quality-enforcement .agents/skills/quality-enforcement && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "quality-enforcement" agent skill from https://github.com/NoobyGains/godmode/tree/master/skills/quality-enforcement into .agents/skills/quality-enforcement/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "quality-enforcement", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add NoobyGains/godmode --skill quality-enforcement -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install NoobyGains/godmode quality-enforcement --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/NoobyGains/godmode.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/quality-enforcement .cursor/skills/quality-enforcement && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "quality-enforcement" agent skill from https://github.com/NoobyGains/godmode/tree/master/skills/quality-enforcement into .cursor/skills/quality-enforcement/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "quality-enforcement", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/NoobyGains/godmode.git --path skills/quality-enforcement--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add NoobyGains/godmode --skill quality-enforcement -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install NoobyGains/godmode quality-enforcement --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/NoobyGains/godmode.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/quality-enforcement .gemini/skills/quality-enforcement && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "quality-enforcement" agent skill from https://github.com/NoobyGains/godmode/tree/master/skills/quality-enforcement into .gemini/skills/quality-enforcement/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "quality-enforcement", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install NoobyGains/godmode quality-enforcementInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add NoobyGains/godmode --skill quality-enforcement -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/NoobyGains/godmode.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/quality-enforcement .github/skills/quality-enforcement && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "quality-enforcement" agent skill from https://github.com/NoobyGains/godmode/tree/master/skills/quality-enforcement into .github/skills/quality-enforcement/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "quality-enforcement", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add NoobyGains/godmode --skill quality-enforcement -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install NoobyGains/godmode quality-enforcement --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/NoobyGains/godmode.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/quality-enforcement .opencode/skills/quality-enforcement && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "quality-enforcement" agent skill from https://github.com/NoobyGains/godmode/tree/master/skills/quality-enforcement into .opencode/skills/quality-enforcement/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "quality-enforcement", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
quality-enforcement- GitHub stars
- 107
- Token cost
- ~2k tokens
- SKILL.md length
- 805 words
- Files
- 1
- Skills in repo
- 34
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when preparing code for commit, PR, or merge - covers linting, type safety, bundle budgets, coverage thresholds, complexity limits, dependency audit, and dead code detection
- Preparing code for commit
- SKILL.md covers Overview, The Prime Directive, When to Use and The Entry Protocol, plus 6 more sections
- Calls npm and cargo
- Merge - covers linting
What it does
Quality Enforcement is an agent skill from NoobyGains/godmode. Use when preparing code for commit, PR, or merge - covers linting, type safety, bundle budgets, coverage thresholds, complexity limits, dependency audit, and dead code detection
Its SKILL.md is about 2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Type safety and Linting and formatting. The repository describes itself as: The AI development framework that thinks before it builds. 36 composable skills for Claude Code, Cursor, Codex, and OpenCode. The licence is MIT.
When your agent uses it
- Preparing code for commit
- Merge - covers linting
- Coverage thresholds
- Complexity limits
Example prompts
- “/quality-enforcement”
Requirements
- Python 3
What it can do on your machine
Read from SKILL.md and the folder at commit 441103a. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
npmcargo
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use npm, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Quality Enforcement loads about 2k tokens when it runs. Until then it costs about 49 tokens; SKILL.md has 805 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from NoobyGains/godmode at commit 441103a, republished under its MIT licence (© NoobyGains). 805 words, ~2,015 tokens.
Download SKILL.mdSave it as
.claude/skills/quality-enforcement/SKILL.md (or your agent's skills folder).- name
- quality-enforcement
- description
- Use when preparing code for commit, PR, or merge - covers linting, type safety, bundle budgets, coverage thresholds, complexity limits, dependency audit, and dead code detection
Quality Enforcement
Overview
Quality enforcement is automated, not aspirational. If it can be checked by a machine, it must be.
Core principle: A quality check that is not enforced in CI does not exist.
No exceptions. No workarounds. No shortcuts.
The Prime Directive
NO CODE LANDS WITHOUT ALL QUALITY CHECKS PASSINGIf a check fails, fix the code. Never disable the check. Never bypass CI.
When to Use
Always before:
- Committing code
- Opening a pull request
- Merging to trunk
- Releasing to production
Especially when:
- "Just suppress the linter this once" (never)
- "CI is too slow, merge manually" (fix CI, do not skip it)
- "Type errors but it works at runtime" (fix the types)
- "Coverage dropped but the critical paths are tested" (restore coverage)
The Entry Protocol
BEFORE any PR or merge:
1. LINT: Zero errors, zero warnings
2. TYPES: Zero type errors (strict mode)
3. TESTS: All passing, coverage meets threshold
4. BUILD: Clean build, no warnings
5. SIZE: Bundle/binary within budget (if applicable)
6. DEPS: No known vulnerabilities (critical/high)
7. COMPLEXITY: No functions exceeding complexity threshold
Any check fails = code is not ready. Fix before advancing.Quality Check Reference
Check 1: Linting
Standard: Zero errors AND zero warnings| Setting | Value | Rationale |
|---|---|---|
| Errors | 0 | Non-negotiable |
| Warnings | 0 | Warnings become errors you learn to ignore |
| Config committed | Yes | Consistent across all contributors |
| CI enforced | Yes | Local overrides are irrelevant |
Warnings are tomorrow's errors. Either fix them or adjust the rule. Never tolerate warnings.
Disable a rule? Only if the team explicitly agrees the rule is inappropriate for this project. Document the rationale in the config file. Never disable inline for convenience.
Check 2: Type Safety
Standard: Zero type errors, strict mode enabledTypeScript:
{
"compilerOptions": {
"strict": true,
"noUncheckedIndexedAccess": true,
"noImplicitReturns": true,
"noFallthroughCasesInSwitch": true,
"forceConsistentCasingInFileNames": true
}
}Python: mypy or pyright with strict mode.
| Anti-Pattern | Problem | Fix |
|---|---|---|
any type | Disables type checking | Use specific types or generics |
// @ts-ignore | Conceals real errors | Fix the type error |
# type: ignore | Same problem | Fix the type error |
| Non-strict mode | False sense of safety | Enable strict from day one |
any is a type error you chose not to resolve. Every any weakens the type system for everything it touches.
Check 3: Test Coverage
Standard: Coverage threshold that never decreases| Metric | Floor | Target |
|---|---|---|
| Line coverage | 80% | 90%+ |
| Branch coverage | 70% | 85%+ |
| New code coverage | 90% | 100% (aspire to) |
Coverage thresholds are a ratchet. They increase, never decrease. Configure CI to fail if coverage drops below the current level.
Coverage is necessary but not sufficient. 100% coverage with poor assertions is worse than 70% coverage with rigorous assertions. Coverage checks combine with TDD discipline (godmode:test-first).
Check 4: Build
Standard: Clean build, zero warnings- Build must complete successfully
- Zero compiler/build warnings
- Output matches expected structure
- No missing dependencies at build time
Check 5: Bundle Size Budget (Frontend)
Standard: Total bundle size within defined budget| Target | Budget | Tool |
|---|---|---|
| Initial JS (compressed) | <200KB | webpack-bundle-analyzer |
| CSS | <50KB | PurgeCSS check |
| Images | Optimized, WebP/AVIF | imagemin |
| Total page weight | <1MB | Lighthouse |
Set the budget. Enforce in CI. When budget is exceeded, analyze the bundle contents and eliminate or split.
Check 6: Dependency Audit
Standard: Zero critical or high vulnerabilities| Language | Command | CI Integration |
|---|---|---|
| JavaScript | npm audit --audit-level=high | Fail on high+ |
| Python | pip-audit or safety check | Fail on high+ |
| Go | govulncheck ./... | Fail on any |
| Rust | cargo audit | Fail on any |
Also verify:
- No unnecessary dependencies (is every dep actually used?)
- No duplicate dependencies (different versions of same package)
- Dependencies are maintained (last update within 12 months)
Show full SKILL.md (345 more words)Show less
Check 7: Complexity Metrics
Standard: No function exceeds complexity threshold| Metric | Threshold | Tool |
|---|---|---|
| Cyclomatic complexity | <10 per function | ESLint (complexity rule), radon, gocyclo |
| Function length | <50 lines | Linter rules |
| File length | <400 lines | Linter rules |
| Parameters | <5 per function | Linter rules |
When complexity exceeds threshold: Refactor. Extract functions. Simplify conditionals. Never raise the threshold.
Check 8: Dead Code
Standard: No unused exports, variables, or dependencies| What | Tool |
|---|---|
| Unused exports | ts-prune, knip |
| Unused dependencies | depcheck, knip |
| Unused variables | Linter (no-unused-vars) |
| Unreachable code | Linter, type checker |
Dead code is misleading code. It implies something depends on it. Remove it.
CI Pipeline Template
# Minimum quality enforcement pipeline
quality-checks:
steps:
- name: Lint
run: npm run lint
- name: Type Check
run: npm run typecheck
- name: Test
run: npm test -- --coverage
- name: Coverage Check
run: check-coverage --threshold 80
- name: Build
run: npm run build
- name: Bundle Size
run: bundlesize
- name: Audit
run: npm audit --audit-level=highAll checks run on every PR. All must pass before merge.
Cognitive Traps
| Rationalization | Truth |
|---|---|
| "Just a lint warning, not an error" | Warnings you ignore become errors you miss. |
| "Type error but it works at runtime" | Types prevent the runtime error you have not encountered yet. |
| "Coverage dropped 1%, not a big deal" | 1% per PR = 50% in a year. Ratchets do not go down. |
| "Skip CI, I tested locally" | Local environments differ from CI. That is why CI exists. |
| "Bundle grew because we added features" | Features should replace or split, not only add. |
| "Vulnerability is in a dev dependency" | Dev deps run in CI. CI has secrets. Still a risk. |
| "Function is complex but readable" | Complexity limits exist because readability is subjective. |
| "Dead code might be needed later" | Git remembers. Delete it. Restore from history if needed. |
Guardrails - HALT and Fix
- Disabling lint rules inline without documented rationale
@ts-ignoreor# type: ignorewithout an accompanying issue- Coverage threshold lowered in config
- CI skipped or overridden for merge
anytypes spreading through codebase- Bundle size growing without investigation
- Warnings treated as acceptable
- Audit failures dismissed because "it's a dev dependency"
All of these mean: The check is broken. Fix the check before writing more code.
Integration
Complements:
- godmode:test-first — Tests are one check among many
- godmode:completion-gate — Quality checks are verification evidence
- godmode:project-bootstrap — Checks configured at project setup
- godmode:security-protocol — Dependency audit is a security check
- godmode:performance-tuning — Bundle size is a performance check
The Bottom Line
Every quality check automated in CI. Every check passing before merge. No exceptions.If a check can be bypassed, it will be bypassed. Make it impossible to bypass.
© NoobyGains, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/quality-enforcement of NoobyGains/godmode.
Open the folder on GitHubat commit 441103a
Compare with similar skills
Quality Enforcement next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Quality Enforcement this skillNoobyGains/godmode | 107 | — | ~2k | Automated safety check: Pass | MIT | |
| Minimizing Ty Ecosystem Changesastral-sh/ruff | 50k | — | ~4.6k | Automated safety check: Pass | MIT | |
| Kedro Babysitkedro-org/kedro | 11k | — | ~4k | Automated safety check: Pass | Custom licence | |
| Setup Pre Commitfossasia/eventyay-interpretation | 1.6k | 12 repos | ~565 | Automated safety check: Pass | Apache-2.0 | |
| Update Dependenciesalorence/django-modern-rpc | 111 | — | ~1.3k | Automated safety check: Pass | MIT | |
| Obsidian Plugin Development Guidelinesgapmiss/obsidian-plugin-skill | 190 | — | ~4.5k | Automated safety check: Pass | MIT |
Similar skills
- Official
Kedro Babysit
kedro-org/kedro
Run Kedro's local lint / format / type-check / tests on changed files (uses the project's pre-commit hooks, ruff, mypy, pytest, lint-imports, detect-secrets, Make targets — in the right venv), or…
Setup Pre Commit
fossasia/eventyay-interpretation
Set up Husky pre-commit hooks with lint-staged (Prettier), type checking, and tests in the current repo.
Update Dependencies
alorence/django-modern-rpc
Routine update of all project dependencies — uv itself, uv.lock (all groups), tool versions pinned in GitHub workflows and .pre-commit-config.yaml (uv, ruff, mypy...), and SHA-pinned GitHub Actions.
Obsidian Plugin Development Guidelines
gapmiss/obsidian-plugin-skill
Rules and references for building Obsidian plugins: ESLint rules, TypeScript practices, memory cleanup, API choices, UI standards and the community submission process.
Ha Code Quality
FutureTense/keymaster
Standards and commands for linting, code formatting, typing validation (Ruff, MyPy, Codespell, ESLint, Pre-commit/Prek, Tox), and adherence to Home Assistant Python 3.14 standards in Keymaster.
More from NoobyGains/godmode
All 34 skills in this repoActivation
NoobyGains/godmode
A skill your agent uses when starting any conversation - establishes how to locate and invoke skills, mandating Skill tool usage before ANY response including clarifying questions
Agent Messaging
NoobyGains/godmode
A skill your agent uses when dispatching subagents, composing prompts for teammates, structuring handoff reports, or managing context boundaries between agents.
Codebase Research
NoobyGains/godmode
A skill your agent uses when building ANY feature within an existing project - search the current codebase for existing patterns, conventions, similar implementations, and established approaches…
Completion Gate
NoobyGains/godmode
A skill your agent uses when about to declare work done, fixed, or passing, before committing or opening PRs - demands executing verification commands and reading their output before making any…
Comprehension Check
NoobyGains/godmode
A skill your agent uses when implementing any substantial feature, multi-file modification, or architectural change - produces a plain-language walkthrough of every alteration so the developer can…
Delegated Execution
NoobyGains/godmode
A skill your agent uses when executing implementation plans with independent tasks in the current session
Related
Categories
Questions about Quality Enforcement
What does Quality Enforcement do?
A skill your agent uses when preparing code for commit, PR, or merge - covers linting, type safety, bundle budgets, coverage thresholds, complexity limits, dependency audit, and dead code detection. Quality Enforcement is an agent skill from NoobyGains/godmode.
When should I use Quality Enforcement?
Quality Enforcement fits situations like: preparing code for commit; merge - covers linting; coverage thresholds; complexity limits.
How do I install Quality Enforcement in Claude Code?
Run `npx skills add NoobyGains/godmode --skill quality-enforcement -a claude-code`. Or copy the skill folder (skills/quality-enforcement in NoobyGains/godmode) into .claude/skills/quality-enforcement in your project. Claude Code loads it when a task matches its description.
How do I install Quality Enforcement in Codex?
Run `npx skills add NoobyGains/godmode --skill quality-enforcement -a codex`. Or copy the skill folder (skills/quality-enforcement in NoobyGains/godmode) into .agents/skills/quality-enforcement in your project. Codex loads it when a task matches its description.
Can I use Quality Enforcement in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add NoobyGains/godmode --skill quality-enforcement -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/quality-enforcement, .gemini/skills/quality-enforcement, .github/skills/quality-enforcement and .opencode/skills/quality-enforcement in your project.
What does Quality Enforcement need to run?
Going by SKILL.md and its folder, Quality Enforcement needs the command-line tools its instructions call (npm and cargo). Our summary lists: Python 3.
Does Quality Enforcement access the network?
SKILL.md contains no URLs. Its commands use npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Quality Enforcement safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Quality Enforcement use?
Quality Enforcement is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Quality Enforcement use?
About 2k tokens (SKILL.md is roughly 8.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Quality Enforcement?
Skills that share tags, products or a category with Quality Enforcement: Minimizing Ty Ecosystem Changes (astral-sh/ruff, 50k stars), Kedro Babysit (kedro-org/kedro, 11k stars), Setup Pre Commit (fossasia/eventyay-interpretation, 1.6k stars) and Update Dependencies (alorence/django-modern-rpc, 111 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Quality Enforcement?
NoobyGains (a GitHub user) maintains it in NoobyGains/godmode, which has 107 GitHub stars. The repository holds 34 skills in this directory. The repository was last updated on March 9, 2026.
Source: NoobyGains/godmode on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.