skills.rest
synaptiai
synaptiaiOFFICIAL
Explore all skills by this author →
WebsiteGitHub

code-quality-principles

Enforce intentional code quality standards and proximity-tested cleanups across modified source files.

6|2|Updated Dec 19, 2025
Search Tags:#linting#code-quality#code-review#atomic-commits#secrets-detection#boy-scout-rule#proximity-test
One-click install
npx skills add https://github.com/synaptiai/synapti-marketplace --skill code-quality-principles
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-quality-principles
Source: https://github.com/synaptiai/synapti-marketplace/tree/main/plugins/flow/skills/code-quality-principles
Command: npx skills add https://github.com/synaptiai/synapti-marketplace --skill code-quality-principles

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a concrete ruleset and operational checklist to prevent accidental, low-quality, or insecure changes during development and autonomous edits by ensuring every change is intentional and reviewable.

Core Features & Use Cases

  • Iron Law: Require intentionality for every change and revert unexplained edits.
  • Boy Scout Rule: Apply small, proximity-tested cleanups to files you already modify and record them as improve: commits when appropriate.
  • Production Standards: Prevent secrets in commits, disallow TODOs and debug prints in shipped code, and avoid mocks/stubs or commented-out code in production.
  • Quality Execution: Run lint, test, and type checks as parallel commands; classify first-touch files and enforce atomic commits and self-review checklists.
  • Use Case: Use this skill to audit a proposed pull request, flag policy violations, and enumerate proximity-eligible cleanups before committing.

Quick Start

Use the code-quality-principles skill to audit a planned change and list any required cleanups, secrets, or policy violations before committing.

Frequently Asked Questions about code-quality-principles

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce atomic commits and prevent secrets from entering my codebase?▼

Atomic commits and secrets detection are enforced by requiring intentionality for every change and scanning modified files to block policy violations before committing. This ensures every edit is reviewable and secure.

What is the Boy Scout rule for code quality and how does proximity testing work?▼

The Boy Scout rule applies small cleanups to files you already modify, while proximity testing ensures cleanups stay limited to nearby code. Eligible improvements are recorded as separate improve: commits.

How do I audit a pull request for debug prints, TODOs, and commented-out code?▼

Auditing a pull request for debug prints and TODOs involves checking modified files against production standards that disallow unfinished code. The review classifies first-touch files and flags violations before committing.

Can I run lint, test, and type checks in parallel during code review?▼

Yes, you can run lint, test, and type checks as parallel commands during code review. This classifies first-touch files and executes quality checks simultaneously to validate changes efficiently.

What is the best way to apply small code cleanups without introducing unintended changes?▼

Applying small cleanups safely requires enforcing intentionality for every change and reverting unexplained edits. Only proximity-tested cleanups within modified files are permitted to prevent accidental side effects.

When should I avoid using mocks, stubs, or commented-out code in production commits?▼

Mocks, stubs, and commented-out code should never be used in production commits because they violate production standards. Enforcing intentional quality rules prevents these artifacts from shipping.

Related Skills

Explore More Software Engineering Skills→
sizukutamagosizukutamago

verified-commit

Run lint, type-check, and tests before commits.

Community
Intermediate
prototypdigitalprototypdigital

workspace-hygiene

Audit git workspace changes before commits and pull requests.

Official
Intermediate
LuisSambranoLuisSambrano
7

code-review

Perform systematic code review and static analysis across multiple programming languages.

Community
Advanced
excattexcatt
14

audit

Execute project-specific verification rules for business logic, architecture, and naming conventions.

Community
Advanced