clean-code-hard-limits-zero-tolerance
Sub-skill of clean-code: Hard Limits (Zero-Tolerance).
Best use case
clean-code-hard-limits-zero-tolerance is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Sub-skill of clean-code: Hard Limits (Zero-Tolerance).
Teams using clean-code-hard-limits-zero-tolerance should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/hard-limits-zero-tolerance/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How clean-code-hard-limits-zero-tolerance Compares
| Feature / Agent | clean-code-hard-limits-zero-tolerance | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Sub-skill of clean-code: Hard Limits (Zero-Tolerance).
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Hard Limits (Zero-Tolerance) ## Hard Limits (Zero-Tolerance) | Metric | Hard Limit | Target | Action When Exceeded | |--------|-----------|--------|----------------------| | File length | **400 lines** | 200 lines | Split by responsibility | | Function length | **50 lines** | 20–30 lines | Extract helpers | | Class public methods | **10 methods** | 5–7 methods | Extract sub-classes or use composition | | Nesting depth | **4 levels** | 2 levels | Extract guard clauses or sub-functions | | Import count per file | **20 imports** | 10–12 imports | Sign of a God Object — split the file | **Exception 1 — Legacy solver**: Low-churn files with full test coverage may remain until a dedicated refactor WRK is approved. Document with `# noqa: clean-code` at the top of the file. **Exception 2 — Pure declarative data**: Files whose content is ≥95% frozen dataclass/dict literals with zero logic (no conditionals, no I/O, no imports from sibling modules) are exempt from the 400L limit. The logic module that consumes them must still be ≤400L. Example: `activity_definitions.py` (1,419L) — 14 `return Activity(...)` builder functions. Test: if every function body is a single `return SomeDataclass(...)`, it is a data file, not a God Object. ---
Related Skills
mnt-analysis-cleanup
Survey, classify, and clean up `/mnt/local-analysis/` (or any sibling-to-workspace-hub directory holding orphan worktrees, codex-burn artifacts, agent log accumulations, and outer-clone duplicates) without losing useful code/work. Surfaces a tiered approval menu rather than baking decisions; defers all destructive ops until user confirms.
blender-worktree-test-hardening
Recover and harden digitalmodel Blender automation work in isolated worktrees when uv/editable dependency paths break and local machines lack a Blender executable.
pre-completion-cleanup-audit
Audit and dispose of session residue (orphan files, scratch dirs, sibling-repo state, locks, trash-stages) BEFORE claiming a task complete. Required gate before any agent says "all done", "task complete", or hands work back to user/orchestrator.
git-worktree-cleanup-at-scale
Identify and remove stale git worktrees blocking branch deletion in multi-repo environments
git-worktree-cleanup-and-branch-reconciliation
Systematic process for cleaning up stale git worktrees, resolving merge conflicts in diverged branches, and reconciling branch state across multiple repositories.
git-worktree-cleanup-and-branch-hygiene
Systematic approach to cleaning up stale git worktrees, orphan branches, and branch hygiene at scale across multiple repos
git-blob-size-filter-cleanup
Strip oversized blobs from unpushed commits using git filter-branch when GitHub's 100 MB limit blocks push
clean-worktree-integration-from-dirty-main
Land validated issue work from isolated worktrees when the main checkout is dirty by creating a fresh integration worktree, cherry-picking only implementation commits, re-running combined validation, and preparing push/closeout artifacts.
clean-code
Clean code enforcement for workspace-hub Python repos: file/function size limits, God Object detection, naming rules, dead code removal, and refactor decision guidance. Consult before writing new modules or accepting large files.
post-smoke-ci-plan-boundary-hardening
Harden a CI follow-up plan after an initial smoke/unblock issue lands. Use for post-smoke red workflows where later gates surface broad lint/type debt and the plan must stay bounded, evidence-backed, and review-honest.
live-writer-branch-cleanup-guard
Guardrails for multi-repo sync and branch cleanup when workspace-hub or another shared repo has active writer sessions, worktree-backed branches, or unrelated-history branches.
iterative-plan-hardening-with-adversarial-waves
Tighten a draft plan through repeated Codex/Gemini adversarial review waves without prematurely advancing it to plan-review.