What are considered 'Red Flags' by this skill?

Red flags include speculative 'future-proofing', defensive checks for impossible failures, and creating complex abstractions for simple, single implementations.

Can I use this for feature implementation?

Absolutely. It ensures that new features match existing patterns and only include the code strictly required for the task at hand.

What is the primary focus of the Reviewing Code skill?

The primary focus is enforcing a senior engineer mindset, ensuring that all code changes are minimal, scoped, and safe for production environments.

Does this skill help prevent bugs?

Yes, by requiring a justification for every file touched and forcing the AI to flag assumptions and risks, it significantly reduces the chance of regressions.

How does this skill handle refactoring?

It actively discourages unnecessary or 'drive-by' refactoring, ensuring that cleanup efforts don't get bundled with feature work or bug fixes.

Reviewing Code & Execution

Name: Reviewing Code & Execution
Author: yallup

byyallup

•

Collaboration Tools

Enforces senior engineer discipline by prioritizing minimal, production-safe changes during code reviews and task execution.

About

The reviewing-code skill transforms Claude into a disciplined senior engineer, focusing on scoped, intentional modifications rather than broad, speculative refactors. It guides the AI through a rigorous process of clarifying scope, identifying precise insertion points, and justifying every file modification to ensure production stability. By eliminating 'future-proofing' and unnecessary complexity, this skill ensures that code changes are efficient, maintainable, and free from common regressions, making it an essential tool for teams prioritizing code quality and stability.

Key Features

Enforces senior engineer discipline for minimal code impact
Requires pre-coding scope clarification and insertion point mapping
Strictly blocks speculative changes and 'drive-by' refactoring
Mandates justification for every file modified during a task
Flags architectural red flags like abstract base classes for single implementations
1 GitHub stars

Use Cases

Conducting rigorous code reviews to maintain high repository standards
Implementing new features with a minimal and focused architectural footprint
Fixing critical bugs without introducing unintended side effects or regressions

About

Key Features

Enforces senior engineer discipline for minimal code impact
Requires pre-coding scope clarification and insertion point mapping
Strictly blocks speculative changes and 'drive-by' refactoring
Mandates justification for every file modified during a task
Flags architectural red flags like abstract base classes for single implementations
1 GitHub stars

Use Cases

Conducting rigorous code reviews to maintain high repository standards
Implementing new features with a minimal and focused architectural footprint
Fixing critical bugs without introducing unintended side effects or regressions