review-and-refactor

Review and refactor source code using repository coding guidelines.

Updated Apr 14, 2026
One-click install
npx skills add https://github.com/BrunoAMSilva/my-config --skill review-and-refactor-brunoamsilva
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-and-refactor
Source: https://github.com/BrunoAMSilva/my-config/tree/main/coding/skills/review-and-refactor
Command: npx skills add https://github.com/BrunoAMSilva/my-config --skill review-and-refactor-brunoamsilva

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Many repositories accumulate technical debt, inconsistent style, and unclear structure over time; this Skill systematically reviews code and applies refactorings so the codebase becomes cleaner, more consistent, and easier to maintain.

Core Features & Use Cases

  • Repository-guided refactorings: Reads repository coding guidelines from .github/instructions/*.md and .github/copilot-instructions.md and applies changes that align with those rules.
  • Non-destructive updates: Improves structure and readability while keeping existing files intact and preserving functionality.
  • Test-aware verification: Runs or verifies existing tests when present to ensure refactors do not break behavior.
  • Use Case: A maintainer wants to align an older project to new style rules and reduce technical debt without reorganizing file layouts.

Quick Start

Run the review-and-refactor skill to read the repository coding instructions, refactor source files to follow those standards without splitting files, and confirm tests still pass if they exist.

Frequently Asked Questions about review-and-refactor

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

FAQPage Schema
How do I refactor source code to improve maintainability without breaking existing functionality?

To refactor source code safely, the review-and-refactor process reads repository coding guidelines, applies targeted edits to improve structure, and verifies existing tests to ensure functionality is preserved.

What is the best way to align an older project codebase to new coding guidelines?

Aligning an older project to new coding guidelines involves reading .github/instructions/*.md and .github/copilot-instructions.md, then applying non-destructive updates that improve readability without splitting files.

How does repository-guided code cleanup handle local coding standards?

Repository-guided code cleanup handles local standards by reading .github/instructions/*.md and .github/copilot-instructions.md files before making targeted edits, ensuring refactors follow provided rules.

Does automated code review preserve file layouts when reducing technical debt?

Automated code review reduces technical debt while keeping existing files intact and preserving functionality, making it suitable for maintainers who want to avoid reorganizing file layouts.

Can I refactor my repository if I only have partial test coverage?

Yes, you can refactor with partial test coverage; the process runs or verifies existing tests when present to prevent breaking behavior, but full coverage is not a strict requirement to begin cleanup.

When should I not use an automated refactoring skill for repository cleanup?

You should avoid automated refactoring if your repository lacks defined coding guidelines in .github/instructions or if you need to completely reorganize file layouts rather than improving readability within existing files.