One-click install
npx skills add https://github.com/abnegate/claudes --skill improve-abnegate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: improve
Source: https://github.com/abnegate/claudes/tree/main/skills/improve
Command: npx skills add https://github.com/abnegate/claudes --skill improve-abnegate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It eliminates the slow, error-prone cycle of reviewing code by helping you systematically find and fix issues across security, performance, correctness, readability, maintainability, and testing.

Core Features & Use Cases

  • Multi-dimension review with fixes: Detects prioritized issues across six quality dimensions and applies concrete improvements, not just commentary.
  • Iterative hardening cycles: Runs one or more improvement passes that raise the severity bar over time to converge toward a cleaner codebase.
  • Consolidated, mergeable repair workflow: Uses parallel worktree-isolated fix branches and a consolidation step to merge changes safely.
  • Use case: Before releasing or after receiving a bug report, run this to harden an existing codebase by addressing critical security/correctness problems first, then improving performance, structure, and test coverage.

Quick Start

Run /improve 2 to perform two iterative improvement cycles and automatically apply fixes with verification and final committing.

Frequently Asked Questions about improve

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

FAQPage Schema
How do I automatically fix bugs and improve code quality before merging?

To automatically fix bugs and improve code quality, you can run an automated refactoring process that reviews your full diff, identifies prioritized issues across security, performance, and correctness, and applies verified fixes before committing.

What is the best way to harden an existing codebase after a CI failure?

The best way to harden an existing codebase after a CI failure is to run iterative hardening cycles that raise the severity bar over time, addressing critical security and correctness problems first before improving structure and test coverage.

Can I review code across multiple dimensions like security and performance simultaneously?

Yes, you can review code across multiple dimensions simultaneously by gathering prioritized issues across security, performance, correctness, readability, maintainability, and testing in parallel before applying concrete improvements.

How does worktree-isolated fixing work when applying automated refactoring?

Worktree-isolated fixing works by creating parallel fix branches for identified issues, applying concrete improvements independently, and then using a consolidation step to merge the changes safely back into your development branch.

Does this code review workflow support iterative improvement passes?

Yes, this code review workflow supports iterative improvement passes, allowing you to specify multiple cycles that systematically converge toward a cleaner codebase by progressively raising the severity floor for accepted issues.

When do I need automated refactoring with post-fix verification?

You need automated refactoring with post-fix verification when you are preparing changes for releases, hardening ongoing development branches, or addressing bug reports and must ensure applied fixes pass validation before committing.