Review and refactor code in your project according to defined instructions
v1.0LATEST
NewUpdated Jun 26, 2026
Role
You're a senior expert software engineer with extensive experience in maintaining projects over a long time and ensuring clean code and best practices.
Task
Take a deep breath, and review all coding guidelines instructions in .github/instructions/*.md and .github/copilot-instructions.md, then review all the code carefully and make code refactorings if needed.
The final code should be clean and maintainable while following the specified coding standards and instructions.
Do not split up the code, keep the existing files intact.
If the project includes tests, ensure they are still passing after your changes.
Files1
1 files · 1.0 KB
Select a file to preview
Overall Score
52/100
Grade
C
Adequate
Grades are signals, not a certification. Always review a skill yourself before use.
Safety
55
Quality
48
Clarity
60
Completeness
42
Summary
A generic code review and refactoring skill that instructs an agent to read project coding guidelines from GitHub directories, then review and refactor code to match those standards while preserving file structure and maintaining test passage. The skill operates without scope boundaries, detailed guardrails, or clear success criteria.
Detected Capabilities
file readfile writeshell executiontest execution
Trigger Keywords
Phrases that agents use to match this skill to user intent.
Broad project-wide code modification without scope boundaries — skill instructs agent to 'review all code carefully and make refactorings' with no limits on files, directories, or change scope
Task section, step 1-3
WARNING
External instruction sourcing — skill delegates instructions to `.github/instructions/*.md` and `.github/copilot-instructions.md`, which are user-supplied and untrusted. No validation or sanitization of these files before following them.
Task section, step 1
WARNING
Test execution without rollback plan — skill runs tests after changes (step 4) but provides no guidance on what to do if tests fail or how to revert problematic changes
Task section, step 4
INFO
Vague success criteria — 'clean and maintainable' is subjective. No definition of 'done', no diff review process, no approval workflow
Task section, step 2
INFO
No error handling documented — skill does not explain how to handle merge conflicts, syntax errors, or breaking changes introduced during refactoring
SKILL.md
Use Cases
]Refactor code to match project style guides
Apply linting and formatting standards across a codebase
Clean up code before project milestone
Ensure adherence to team coding standards
Quality Notes
Positive: Includes guardrail to preserve file structure ('keep the existing files intact')
Positive: Acknowledges test responsibility ('ensure tests are still passing')
Negative: No documentation of what the skill will actually do step-by-step (what refactorings? what patterns?)
Negative: No guidance on change scope — will it modify all files or only specific patterns?
Negative: No examples of expected outputs or before/after code comparisons
Negative: Relies entirely on external instruction files without validation — if those files are malformed or contradictory, the skill has no fallback
Negative: No mention of dry-run mode, code review, or approval gates — agent makes changes directly
Negative: The 'Role' section (senior engineer persona) is motivational but adds no technical detail
Model: claude-haiku-4-5-20251001Analyzed: Jun 26, 2026
Reviews
Add this skill to your library to leave a review.
No reviews yet
Be the first to share your experience.
Use github/review-and-refactor in your dev environment — a Developer account adds skills to your library and syncs them via the SkillRepo CLI.