senior-developer

Review code changes for scope, conventions, and regression risks.

Updated Apr 27, 2026
One-click install
npx skills add https://github.com/badowhp/skill-mania --skill senior-developer-badowhp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: senior-developer
Source: https://github.com/badowhp/skill-mania/tree/main/plugins/skill-mania/skills/senior-developer
Command: npx skills add https://github.com/badowhp/skill-mania --skill senior-developer-badowhp

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill eliminates the risk of unscoped, unverified, or convention-breaking code changes that introduce regressions, technical debt, and misalignment with existing repository architecture and standards.

Core Features & Use Cases

  • Scoped Code Work: Handles implementation, bug fixes, refactoring, test coverage additions, and local code tradeoffs with minimal, localized changes that respect existing code patterns.
  • Rigorous Code Review: Leads reviews with correctness, regression risks, missing tests, and maintainability issues, separating functional risks from stylistic preferences.
  • Structured Debugging: Guides reproduction, root cause analysis, targeted fixes, and regression test addition to prevent recurring bugs.
  • Use Case: For example, if you need to fix a failing pagination feature in your codebase, this Skill guides you to reproduce the issue, make the smallest possible fix aligned with existing patterns, add a regression test, and verify the change without touching unrelated modules.

Quick Start

Use the senior-developer skill to fix the reported login validation bug, add a regression test, and verify the fix with your repository's existing test suite.

Frequently Asked Questions about senior-developer

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

FAQPage Schema
How do I fix a bug without introducing regressions or breaking existing codebase patterns?

To prevent regressions during bug fixes, apply minimal localized changes that respect existing repository patterns, add targeted regression tests, and verify the fix against your existing test suite.

What is the best way to review code for maintainability and missing tests?

The best way to review code is to evaluate correctness, regression risks, missing tests, and maintainability issues, explicitly separating functional risks from stylistic preferences.

How do I refactor code while minimizing technical debt?

To refactor code while minimizing technical debt, enforce minimal localized changes, track explicit assumptions, and maintain strict adherence to existing repository patterns and conventions.

Does this approach work for local code tradeoff analysis in an existing repository?

Yes, this approach works for local code tradeoff analysis by evaluating minimal localized changes, tracking explicit assumptions, and reporting verification results and remaining risks for repository codebases.

Why should I use scoped debugging instead of modifying unrelated modules?

You should use scoped debugging to guide reproduction, perform root cause analysis, apply targeted fixes, and add regression tests, ensuring you prevent recurring bugs without touching unrelated modules.

When do I need to add regression testing during code implementation?

You need to add regression testing during code implementation whenever you apply bug fixes, refactoring, or test coverage additions to prevent recurring bugs and verify that changes do not break existing functionality.