resolve-issue
Provides a systematic workflow for resolving GitHub Issues. Use this skill when assigned a GitHub Issue or when delegated by the Issue Auto-resolver.
When & Why to Use This Skill
This Claude skill automates the end-to-end GitHub issue resolution process through a systematic, multi-step workflow. It intelligently categorizes incoming issues—ranging from bug fixes and feature requests to documentation and refactoring—and applies specialized protocols for each. By integrating with Git repository workflows and debugging processes, it ensures that code changes are implemented, tested, and documented with consistent pull request descriptions and commit messages, significantly reducing manual overhead for maintainers.
Use Cases
- Automated Bug Triaging and Fixing: Automatically analyze bug reports, trace errors using structured debugging processes, and implement verified fixes following a systematic protocol.
- Streamlined Feature Implementation: Transition seamlessly from a feature request issue to a completed pull request by following guided steps for design evaluation and code generation.
- Standardized Repository Maintenance: Handle routine refactoring, documentation updates, and investigation tasks with a consistent workflow that ensures all PRs and commits meet project standards.
- Delegated Issue Resolution: Act as a specialized agent to resolve tasks assigned by higher-level issue auto-resolvers or project managers within the GitHub ecosystem.
| name | resolve-issue |
|---|---|
| description | Provides a systematic workflow for resolving GitHub Issues. Use this skill when assigned a GitHub Issue or when delegated by the Issue Auto-resolver. |
Resolve Issue
Instructions
Step 1: Determine Issue Type
Check if the Issue has a type:* label. If not, determine the type from the title and body:
| Label | Description |
|---|---|
type:bug |
Fix bugs, errors, or defects |
type:feature |
Add new features |
type:enhancement |
Improve existing features |
type:refactoring |
Code refactoring |
type:documentation |
Update documentation |
type:investigation |
Investigation or analysis tasks |
Default to type:feature if unclear.
Step 2: Follow Type-Specific Instructions
Refer to the corresponding file at {plugin_base_path}/issue-types/<type>.md:
bug.md- Bug fixesfeature.md- New featuresenhancement.md- Feature improvementsrefactoring.md- Code refactoringdocumentation.md- Documentation updatesinvestigation.md- Investigation tasks
Related Skills
This skill works with the following dev-guidelines skills:
| Skill | When to Use |
|---|---|
dev-guidelines:git-repository-workflow |
Git branch management and testing |
dev-guidelines:pr-description-format |
Creating PRs with gh pr create |
dev-guidelines:debugging-process |
Investigating bugs and tracing errors |
dev-guidelines:design-alternatives |
Evaluating implementation approaches |
Notes
{plugin_base_path}refers to the plugin installation directory- Language: Unless otherwise specified, write all Issue comments, PR titles, PR descriptions, and commit messages in Japanese (日本語で記述)