mk:clean-code — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited mk:clean-code (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Be concise, direct, and solution-focused.
For post-implementation complexity reduction within the current diff (Phase 3.5 workflow), usemk:simplify.mk:clean-codeis for broader quality-standards enforcement at any phase.
| Principle | Rule |
|---|---|
| SRP | Single Responsibility — each function/class does ONE thing |
| DRY | Don't Repeat Yourself — extract duplicates, reuse |
| KISS | Keep It Simple — simplest solution that works |
| YAGNI | You Aren't Gonna Need It — don't build unused features |
| Boy Scout | Leave code cleaner than you found it |
references/coding-standards.md for detailed rules| Reference | When to load | Content |
|---|---|---|
| [coding-standards.md](./references/coding-standards.md) | Step 3 — applying standards | Naming, functions, structure, anti-patterns, verification scripts |
| Do | Don't |
|---|---|
| Write code directly | Write tutorials |
| Let code self-document | Add obvious comments |
| Fix bugs immediately | Explain the fix first |
| Inline small things | Create unnecessary files |
| Name things clearly | Use abbreviations |
| Keep functions small | Write 100+ line functions |
The user wants working code, not a programming lesson.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.