Ejecuta cualquier Skill en Manus
con un clic

Ejecuta cualquier Skill en Manus con un clic

fix-issue

Estrellas0

Forks0

Actualizado23 de febrero de 2026 a las 01:21

Fix a GitHub issue end-to-end. Use when given an issue number to fix, implementing bug fixes, or addressing reported problems.

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Ejecutar en Manus

Fuente

yu-iskw

yu-iskw/agentlint

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ejecutar en Manus

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Desarrolladores de softwareOcupaciones informáticas y matemáticas·SOC 15-1252

SKILL.md

readonly

name	fix-issue
description	Fix a GitHub issue end-to-end. Use when given an issue number to fix, implementing bug fixes, or addressing reported problems.

Fix GitHub Issue

Purpose

A complete workflow for fixing GitHub issues from understanding the problem to creating a pull request.

Arguments

$ARGUMENTS: GitHub issue number (e.g., 123 or #123)

Workflow

1. Understand the Issue

gh issue view $ARGUMENTS

Analyze:

What is the reported problem?
What is the expected behavior?
What is the actual behavior?
Are there reproduction steps?

2. Research the Codebase

Search for relevant code:

# Search for keywords from the issue
grep -r "keyword" src/

# Find related files
find . -name "*.py" | xargs grep -l "related_term"

Understand:

Which files are involved?
What is the current implementation?
Where does the bug originate?

3. Create Feature Branch

git checkout -b fix/issue-$ARGUMENTS-<brief-description>

4. Implement the Fix

Apply the minimum necessary change to resolve the issue:

Fix the root cause, not symptoms
Don't refactor unrelated code
Keep changes focused and reviewable

5. Add/Update Tests

Create tests that:

Reproduce the original bug (should fail without fix)
Verify the fix works (should pass with fix)
Cover edge cases

6. Verify the Fix

Run the verification cycle:

make lint
make test
make build

Or invoke the verifier subagent for comprehensive validation.

7. Commit Changes

git add <specific-files>
git commit -m "fix(scope): brief description

Fixes #$ARGUMENTS"

8. Create Pull Request

git push -u origin fix/issue-$ARGUMENTS-<brief-description>

gh pr create --title "fix(scope): description" --body "$(cat <<'EOF'
## Summary
Fixes #$ARGUMENTS

## Problem
[Description of the issue]

## Solution
[How this PR fixes it]

## Testing
- [ ] Added test case for the bug
- [ ] All tests pass
- [ ] Manually verified the fix

## Changes
- [List specific changes]
EOF
)"

Example

Input: /fix-issue 42

Workflow:

gh issue view 42 - User reports "import fails with ModuleNotFoundError"
Search for import handling code
git checkout -b fix/issue-42-import-error
Fix the import path in src/your_package/__init__.py
Add test: test_import_module.py
make lint && make test
git commit -m "fix(imports): resolve ModuleNotFoundError\n\nFixes #42"
Create PR with reference to issue

Quick Reference

Task	Command
View issue	`gh issue view <number>`
List issues	`gh issue list`
Create branch	`git checkout -b fix/issue-<n>-<desc>`
Link PR to issue	Include `Fixes #<n>` in commit message
Close issue via PR	Include `Closes #<n>` in PR body

Más de este repositorio

mismo repositorio

build-and-fix

yu-iskw/agentlint

Build the project and automatically fix any build errors, compilation failures, or type mismatches. Use when the project fails to build, shows "broken" states, or after making significant changes.

2026-02-230

clean-project

yu-iskw/agentlint

Perform a "hard reset" of the development environment. Use when dependencies are corrupted, lockfiles are out of sync, or environment tools (Trunk/uv) are in an inconsistent state.

2026-02-230

improve-claude-config

yu-iskw/agentlint

Self-improvement skill for evolving Claude Code configuration. Use when you notice repeated mistakes, want to add new workflows, or optimize the development experience. Enables Claude to improve its own CLAUDE.md, skills, hooks, and agents.

2026-02-230

lint-and-fix

yu-iskw/agentlint

Run linters and fix violations, formatting errors, or style mismatches using Trunk. Use when code quality checks fail, before submitting PRs, or to repair "broken" linting states.

2026-02-230

manage-adr

yu-iskw/agentlint

Manage Architecture Decision Records (ADRs) using adr-tools. Use this to initialize, create, list, and link ADRs to document architectural evolution.

2026-02-230

manage-changelog

yu-iskw/agentlint

Manage changelogs using Changie. Provides tools to initialize, add change fragments, batch releases, and merge version notes.

2026-02-230

name	fix-issue
description	Fix a GitHub issue end-to-end. Use when given an issue number to fix, implementing bug fixes, or addressing reported problems.

Fix GitHub Issue

Purpose

A complete workflow for fixing GitHub issues from understanding the problem to creating a pull request.

Arguments

$ARGUMENTS: GitHub issue number (e.g., 123 or #123)

Workflow

1. Understand the Issue

gh issue view $ARGUMENTS

Analyze:

What is the reported problem?
What is the expected behavior?
What is the actual behavior?
Are there reproduction steps?

2. Research the Codebase

Search for relevant code:

# Search for keywords from the issue
grep -r "keyword" src/

# Find related files
find . -name "*.py" | xargs grep -l "related_term"

Understand:

Which files are involved?
What is the current implementation?
Where does the bug originate?

3. Create Feature Branch

git checkout -b fix/issue-$ARGUMENTS-<brief-description>

4. Implement the Fix

Apply the minimum necessary change to resolve the issue:

Fix the root cause, not symptoms
Don't refactor unrelated code
Keep changes focused and reviewable

5. Add/Update Tests

Create tests that:

Reproduce the original bug (should fail without fix)
Verify the fix works (should pass with fix)
Cover edge cases

6. Verify the Fix

Run the verification cycle:

make lint
make test
make build

Or invoke the verifier subagent for comprehensive validation.

7. Commit Changes

git add <specific-files>
git commit -m "fix(scope): brief description

Fixes #$ARGUMENTS"

8. Create Pull Request

git push -u origin fix/issue-$ARGUMENTS-<brief-description>

gh pr create --title "fix(scope): description" --body "$(cat <<'EOF'
## Summary
Fixes #$ARGUMENTS

## Problem
[Description of the issue]

## Solution
[How this PR fixes it]

## Testing
- [ ] Added test case for the bug
- [ ] All tests pass
- [ ] Manually verified the fix

## Changes
- [List specific changes]
EOF
)"

Example

Input: /fix-issue 42

Workflow:

gh issue view 42 - User reports "import fails with ModuleNotFoundError"
Search for import handling code
git checkout -b fix/issue-42-import-error
Fix the import path in src/your_package/__init__.py
Add test: test_import_module.py
make lint && make test
git commit -m "fix(imports): resolve ModuleNotFoundError\n\nFixes #42"
Create PR with reference to issue

Quick Reference

Task	Command
View issue	`gh issue view <number>`
List issues	`gh issue list`
Create branch	`git checkout -b fix/issue-<n>-<desc>`
Link PR to issue	Include `Fixes #<n>` in commit message
Close issue via PR	Include `Closes #<n>` in PR body