review-and-refactor

Popular

Review and refactor code in your project according to defined instructions

36Kstars

0forks

Updated 7/11/2026

Get Skill Source Code

Related Skills

receiving-code-review233K

incremental-implementation77K

hyperframes-animation31K

SKILL.md

readonlyread-only

name

review-and-refactor

description

Review and refactor code in your project according to defined instructions

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.

ponytail

79Kcode-generation

Forces the laziest solution that actually works, simplest, shortest, most minimal. Channels a senior dev who has seen everything: question whether the task needs to exist at all (YAGNI), reach for the standard library before custom code, native platform features before dependencies, one line before fifty. Supports intensity levels: lite, full (default), ultra. Use on ANY coding task: writing, adding, refactoring, fixing, reviewing, or designing code, and choosing libraries or dependencies. Also use whenever the user says "ponytail", "be lazy", "lazy mode", "simplest solution", "minimal solution", "yagni", "do less", or "shortest path", or complains about over-engineering, bloat, boilerplate, or unnecessary dependencies. Do NOT use for non-coding requests (general knowledge, prose, translation, summaries, recipes).

dietrichgebert

Get

golang-dependency-injection

2.3Kcode-generation

Comprehensive guide for dependency injection (DI) in Golang. Covers why DI matters (testability, loose coupling, separation of concerns, lifecycle management), manual constructor injection, and DI library comparison (google/wire, uber-go/dig, uber-go/fx, samber/do). Use this skill when designing service architecture, setting up dependency injection, refactoring tightly coupled code, managing singletons or service factories, or when the user asks about inversion of control, service containers, or wiring dependencies in Go. For a specific DI library, → See `samber/cc-skills-golang@golang-google-wire`, `samber/cc-skills-golang@golang-uber-dig`, `samber/cc-skills-golang@golang-uber-fx`, or `samber/cc-skills-golang@golang-samber-do` skills.