Orchestrate iterative code quality improvement cycles with adversarial discussions.
npx skills add https://github.com/sqfzy/my_configs --skill improve-sqfzy
Please help me install this Agent Skill. Skill: improve Source: https://github.com/sqfzy/my_configs/tree/main/claude/skills/improve Command: npx skills add https://github.com/sqfzy/my_configs --skill improve-sqfzy
Structured code quality improvement cycle helps teams identify latent issues, discuss them adversarially, and capture lessons learned, turning maintenance into a disciplined, measurable process.
Specify a target file or module to start the improvement cycle and run the iterative reviews until convergence.
High-intent search queries and answers about installing and using this skill.
A structured code quality improvement cycle identifies latent issues through global assessment, discusses them adversarially, and captures lessons learned. This turns ongoing maintenance into a disciplined, measurable process across your modules.
The best way to clean up technical debt is using an iterative improvement process with multi-role discussion, implementation, and verification. It automatically saves code health check reports to .artifacts/ upon trigger events.
An adversarial discussion loop for code review surfaces design flaws by forcing multi-role debate over identified issues. It maps global architecture to ensure iterative reviews converge toward measurable software improvement.
Yes, you can specify target files, depth, and auto mode to start the improvement cycle. This allows you to run iterative reviews on specific modules until the code quality convergence is reached.
You need a structured code maintenance process when managing ongoing tech debt cleanup across large modules. Unlike ad-hoc refactoring, it provides iterative verification, multi-role discussion, and auto-saved improvement reports.
ryanthedevIdentify safe refactoring opportunities and produce a structured plan.
ambroviaLog project observations, failures, and successes into structured JSONL files.
nicolanoviellReview code changes for bugs, style issues, and best practices.
smallnestControl multiple AI coding assistants via shell commands and PTY.
