sheriff-is-in-town

Identify universal architectural law violations in code repositories with file and line details.

4|Updated Jan 12, 2017
One-click install
npx skills add https://github.com/brandon-fryslie/dotfiles --skill sheriff-is-in-town
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sheriff-is-in-town
Source: https://github.com/brandon-fryslie/dotfiles/tree/main/config/claude/skills/sheriff-is-in-town
Command: npx skills add https://github.com/brandon-fryslie/dotfiles --skill sheriff-is-in-town

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill identifies violations of universal architectural laws in code repositories, providing a report on where the code breaks these laws without making any fixes.

Core Features & Use Cases

  • Code Audit: Reports violations of architectural laws in code repositories.
  • Read-only Findings: Identifies law violations without altering the code.
  • Law Citing: Cites the specific law violated with file and line information.
  • Use Case: When a user wants to perform a lawfulness pass on a codebase before a refactor or merge, or to understand where the code breaks architectural laws.

Quick Start

Run the 'sheriff-is-in-town' skill to audit the codebase for law violations.

Frequently Asked Questions about sheriff-is-in-town

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

FAQPage Schema
How do I audit my codebase for architectural law violations before a merge?

To audit a codebase for architectural law violations, run a lawfulness pass to identify rule breaks. This generates a read-only report citing the specific law violated alongside the exact file and line information.

What is a lawfulness pass in code analysis?

A lawfulness pass in code analysis is a read-only audit that identifies violations of universal architectural laws within a repository. It reports where the code breaks these laws without making any fixes or altering the codebase.

How does a code audit report architectural compliance issues?

A code audit reports architectural compliance issues by scanning the repository and generating a read-only findings document. It cites the specific universal architectural law violated and provides the exact file and line information for each violation.

Can I use a codebase analysis tool to identify architectural violations without altering the code?

Yes, you can use a codebase analysis tool to identify architectural violations without altering the code. It operates in a read-only mode, providing a report on law violations with specific file and line information while leaving the original code untouched.

When do I need to perform an architectural compliance check on my code repository?

You need to perform an architectural compliance check on your code repository before significant changes such as a refactor or merge. It helps you understand exactly where the code breaks universal architectural laws prior to proceeding with modifications.

Does a code audit automatically fix architectural law violations it finds?

No, a code audit does not automatically fix architectural law violations it finds. It provides a read-only report identifying the specific law violated and the corresponding file and line information, requiring manual intervention to implement any fixes.