convention-enforcer

Audits and fixes code convention violations across multi-package repositories.

1|Updated Jan 13, 2023
One-click install
npx skills add https://github.com/theodrosyimer/.dotfiles --skill convention-enforcer-theodrosyimer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: convention-enforcer
Source: https://github.com/theodrosyimer/.dotfiles/tree/main/claude/skills/dev__convention-enforcer
Command: npx skills add https://github.com/theodrosyimer/.dotfiles --skill convention-enforcer-theodrosyimer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Enforcing consistent coding standards across large monorepos is time‑consuming and error‑prone, leading to scattered violations and broken builds.

Core Features & Use Cases

  • Convention Discovery: Automatically locate or ask for rule definitions, merging them with user‑specified scopes.
  • Parallel Auditing & Fixing: Spawn subagents to audit each module, plan tiered fixes, and verify with test suites and type‑checking.
  • User‑Controlled Planning: Presents a detailed violation summary and waits for approval before any code changes.

Quick Start

Ask the convention‑enforcer skill to enforce naming conventions in the booking module.

Frequently Asked Questions about convention-enforcer

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

FAQPage Schema
How do I audit and fix code convention violations across a monorepo?

To audit and fix code conventions in a monorepo, this skill automatically locates rule definitions, spawns parallel subagents to scan modules, and presents a violation summary for your approval before applying fixes.

What is the best way to enforce consistent coding standards in multi-package repositories?

Enforcing coding standards in multi-package repositories is done by spawning parallel subagents to audit each module against defined rule files, verifying fixes with test suites and type-checking without modifying files outside boundaries.

Can I use automated convention enforcement without modifying files outside module boundaries?

Automated convention enforcement is designed to strictly respect module boundaries, ensuring subagents execute tests and type-checking while planning fixes only within the approved scope.

How does parallel auditing work for shared code in a monorepo?

Parallel auditing works by spawning subagents to scan core and shared code simultaneously, merging discovered rules with user-specified scopes to identify violations and plan tiered fixes.

Do I need existing rule files to automate code convention fixes?

You do not need existing rule files to automate fixes; the skill can automatically locate rule definitions or ask for user-provided conventions to merge with your specified scopes.

Why does automated code convention fixing require user approval before applying changes?

Automated code convention fixing requires user approval because the skill presents a detailed violation summary and waits for your explicit confirmation before planning and executing any tiered code changes.