Guide teams through a repeatable process for identifying and fixing codebase bugs.
npx skills add https://github.com/cyberelf/agent_skills --skill issue-fixer
Please help me install this Agent Skill. Skill: issue-fixer Source: https://github.com/cyberelf/agent_skills/tree/main/skills/issue-fixer Command: npx skills add https://github.com/cyberelf/agent_skills --skill issue-fixer
This skill provides a repeatable, low-risk approach to diagnosing and fixing software issues. It helps teams register issues, perform root-cause analysis, assess impact, implement minimal changes, and validate fixes with unit and end-to-end tests.
Register a new issue in .issues/opening.md for the reported bug and start the Investigation phase.
High-intent search queries and answers about installing and using this skill.
Structured bug fixing minimizes risk by enforcing root-cause analysis, impact assessment, surgical code changes, and validation through unit and end-to-end tests before deployment. Register issues in .issues/opening.md, document decisions, and validate fixes systematically to ensure quality.
Track issues in .issues/opening.md with decision records and traceability. This disciplined approach ensures all team members follow a repeatable process for registration, analysis, implementation, and validation, reducing duplicate efforts and maintaining a shared issue history.
Root-cause analysis follows a structured investigation phase where you register the issue, assess its impact on backend and frontend systems, identify the minimal changes needed, and validate with unit tests and end-to-end tests before implementation.
Yes. The skill covers end-to-end testing across both backend and frontend environments, providing a unified process for diagnosing and fixing issues regardless of where they occur in your stack.
Use unit tests for isolated code changes and end-to-end tests for fixes affecting system workflows or user-facing behavior. The skill enforces validation with both, ensuring quality across different scopes of change and impact.
Impact assessment before implementation identifies dependencies and side effects. If impact is wider than anticipated, the structured process allows you to adjust scope, document decisions in .issues/opening.md, and extend validation across affected components before deployment.
inehemiasmAnalyze Android projects and create testing strategies with test infrastructure setup.
LerianStudioAnalyze development cycle metrics and outcomes to identify improvement patterns.
genesis-agentsCoordinate Jest, Vitest, and Playwright tests across CI/CD pipelines.
AscendAnalyze software errors and generate minimal-diff patches with regression tests.
