fix-issue
Standardized workflow for identifying and patching bugs with minimal regression risk.
Install
mkdir -p .claude/skills/fix-issue-majidraza1228 && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/12613" && unzip -o skill.zip -d .claude/skills/fix-issue-majidraza1228 && rm skill.zipInstalls to .claude/skills/fix-issue-majidraza1228
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Reproduce a bug, implement the smallest correct fix, and verify the result with focused testing.Key capabilities
- →Identify failing behavior from issues, logs, or reproduction steps.
- →Read the smallest set of files to understand the bug.
- →Reproduce the bug with a test, command, or verification step.
- →Implement the smallest fix addressing the root cause.
- →Run focused verification, then broader checks.
- →Summarize the root cause, fix, and verification.
How it works
The skill follows a systematic workflow to reproduce a bug, identify its root cause, implement a minimal fix, and verify the solution. It prioritizes focused changes and clear documentation.
Inputs & outputs
When to use fix-issue
- →Fixing a reported bug
- →Diagnosing a production issue
- →Creating a regression test
About this skill
Fix Issue
Workflow
- Identify the failing behavior from the issue, logs, or reproduction steps.
- Read the smallest set of files needed to understand the bug.
- Reproduce the bug with a test, command, or concrete verification step.
- Implement the smallest fix that addresses the root cause.
- Run focused verification first, then broader checks when warranted.
- Summarize the root cause, the fix, and the verification performed.
Rules
- Do not refactor unrelated code while fixing the issue.
- Prefer a failing test before the fix when the repo has a test harness.
- If the bug cannot be reproduced, say so clearly and document what was checked.
- Remove only dead code made obsolete by the fix itself.
When not to use it
- →When the task involves refactoring unrelated code.
- →When the bug cannot be reproduced and the user expects a fix.
- →When the task involves removing code not made obsolete by the fix itself.
Limitations
- →It does not refactor unrelated code while fixing the issue.
- →It prefers a failing test before the fix when a test harness exists.
- →It only removes dead code made obsolete by the fix itself.
How it compares
This skill enforces a disciplined approach to bug fixing by requiring reproduction, minimal changes, and focused verification, which helps prevent the introduction of new issues often associated with broad, unverified refactoring.
Compared to similar skills
fix-issue side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| fix-issue (this skill) | 0 | 3mo | No flags | Intermediate |
| python-testing-patterns | 77 | 2mo | Review | Intermediate |
| chrome-devtools | 41 | 7mo | Review | Intermediate |
| bats | 9 | 7mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
python-testing-patterns
wshobson
Implement comprehensive testing strategies with pytest, fixtures, mocking, and test-driven development. Use when writing Python tests, setting up test suites, or implementing testing best practices.
chrome-devtools
mrgoonie
Browser automation, debugging, and performance analysis using Puppeteer CLI scripts. Use for automating browsers, taking screenshots, analyzing performance, monitoring network traffic, web scraping, form automation, and JavaScript debugging.
bats
OleksandrKucherenko
Bash Automated Testing System (BATS) for TDD-style testing of shell scripts. Use when: (1) Writing unit or integration tests for Bash scripts, (2) Testing CLI tools or shell functions, (3) Setting up test infrastructure with setup/teardown hooks, (4) Mocking external commands (curl, git, docker), (5) Generating JUnit reports for CI/CD, (6) Debugging test failures or flaky tests, (7) Implementing test-driven development for shell scripts.
browser-daemon
noiv
Persistent browser automation via Playwright daemon. Keep a browser window open and send it commands (navigate, execute JS, inspect console). Perfect for interactive debugging, development, and testing web applications. Use when you need to interact with a browser repeatedly without opening/closing it.
performance-profiling
davila7
Performance profiling principles. Measurement, analysis, and optimization techniques.
obsidian-local-dev-loop
jeremylongshore
Configure Obsidian plugin development with hot-reload and fast iteration. Use when setting up development workflow, configuring test vaults, or establishing a rapid development cycle. Trigger with phrases like "obsidian dev loop", "obsidian hot reload", "obsidian development workflow", "develop obsidian plugin".