ワンクリックでManusで任意のスキルを実行

bugfix

スター18

フォーク0

更新日2025年12月26日 09:47

Automatically fix GitHub issues labeled as 'bug'. Fetches bug issues, analyzes them, implements fixes, and creates PRs against the main branch.

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

agenticdevops

agenticdevops/aof

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

Bug Fix Automation

What This Skill Does

Automates the bug fixing workflow by:

Fetching GitHub issues labeled as "bug"
Analyzing the issue and understanding the problem
Implementing the fix
Running tests to verify the fix
Creating a PR against the main branch

Quick Start

When invoked, this skill will:

Fetch bug issues from the current repository
Present issues for selection (or work on the most recent one)
Analyze the bug by reading related code
Implement the fix with proper testing
Create a PR with detailed description

Step-by-Step Process

Step 1: Fetch Bug Issues

# List all open bug issues
gh issue list --label "bug" --state open --json number,title,body,labels,createdAt --limit 20

Step 2: Select and Analyze Issue

For each bug issue, analyze:

Issue title and description
Steps to reproduce
Expected vs actual behavior
Related code files mentioned
Stack traces or error messages

Step 3: Create Fix Branch

# Create a branch for the fix
git checkout -b fix/issue-<number>-<short-description>

Step 4: Implement the Fix

Locate the relevant code files
Understand the root cause
Implement the minimal fix
Add or update tests
Run the test suite

Step 5: Create Pull Request

# Stage and commit changes
git add -A
git commit -m "fix: <description> (fixes #<issue-number>)"

# Push and create PR
git push -u origin fix/issue-<number>-<short-description>

gh pr create \
  --title "fix: <description>" \
  --body "## Summary
Fixes #<issue-number>

## Changes
- <change 1>
- <change 2>

## Testing
- [ ] Unit tests pass
- [ ] Manual testing completed

## Checklist
- [ ] Code follows project style
- [ ] Tests added/updated
- [ ] Documentation updated if needed"

Execution Instructions

When this skill is invoked, follow these steps:

1. Get Repository Info

gh repo view --json owner,name,defaultBranchRef

2. List Bug Issues

gh issue list --label "bug" --state open --json number,title,body,createdAt,url --limit 10

3. For Each Bug (or Selected Bug):

a) Read the issue details:

gh issue view <number> --json title,body,comments

b) Create a fix branch:

git checkout main
git pull origin main
git checkout -b fix/issue-<number>-<short-slug>

c) Analyze and implement:

Search codebase for related files
Read the relevant code
Understand the bug
Implement the fix
Write/update tests

d) Verify the fix:

# For Rust projects
cargo test
cargo clippy

# For Node projects
npm test
npm run lint

e) Commit and push:

git add -A
git commit -m "fix: <description>

Fixes #<issue-number>"
git push -u origin fix/issue-<number>-<short-slug>

f) Create the PR:

gh pr create --base main --title "fix: <title>" --body "<body>"

Issue Selection

If multiple bug issues exist, present them to the user:

Found N open bug issues:

1. #123 - Login fails with special characters
   Created: 2 days ago

2. #118 - API returns 500 on empty request
   Created: 5 days ago

3. #115 - Memory leak in worker process
   Created: 1 week ago

Which issue would you like to work on? (Enter number or 'all' for batch mode)

PR Template

Use this template for bug fix PRs:

## Summary

Fixes #<issue-number>

## Problem

<Brief description of the bug>

## Solution

<Description of the fix and why it works>

## Changes

- <File 1>: <What changed>
- <File 2>: <What changed>

## Testing

- [ ] Existing tests pass
- [ ] New tests added for the fix
- [ ] Manually verified the fix

## Screenshots/Logs

<If applicable, add before/after screenshots or log output>

Best Practices

Minimal Changes: Only fix the bug, don't refactor unrelated code
Add Tests: Every bug fix should include a test that would have caught it
Link Issues: Always reference the issue number in commits and PR
Verify First: Run tests before creating the PR
Clear Description: Explain the root cause and the fix

Troubleshooting

No bug issues found

# Check if label exists
gh label list | grep -i bug

# Create bug label if missing
gh label create bug --color d73a4a --description "Something isn't working"

Authentication issues

# Check gh auth status
gh auth status

# Re-authenticate if needed
gh auth login

Branch already exists

# Delete local branch and recreate
git branch -D fix/issue-<number>-<slug>
git checkout -b fix/issue-<number>-<slug>

このリポジトリの他の Skills

同じリポジトリ

argocd-deploy

agenticdevops/aof

ArgoCD deployment and rollback operations

2026-02-1418

argocd-sync

agenticdevops/aof

ArgoCD application management, sync operations, and GitOps troubleshooting

2026-02-1418

database-debug

agenticdevops/aof

Database debugging and query execution

2026-02-1418

docker-operations

agenticdevops/aof

Docker container management and troubleshooting

2026-02-1418

git-operations

agenticdevops/aof

Git repository operations and troubleshooting

2026-02-1418

http-testing

agenticdevops/aof

HTTP API testing and debugging

2026-02-1418

name	bugfix
description	Automatically fix GitHub issues labeled as 'bug'. Fetches bug issues, analyzes them, implements fixes, and creates PRs against the main branch.

Bug Fix Automation

What This Skill Does

Automates the bug fixing workflow by:

Fetching GitHub issues labeled as "bug"
Analyzing the issue and understanding the problem
Implementing the fix
Running tests to verify the fix
Creating a PR against the main branch

Quick Start

When invoked, this skill will:

Fetch bug issues from the current repository
Present issues for selection (or work on the most recent one)
Analyze the bug by reading related code
Implement the fix with proper testing
Create a PR with detailed description

Step-by-Step Process

Step 1: Fetch Bug Issues

# List all open bug issues
gh issue list --label "bug" --state open --json number,title,body,labels,createdAt --limit 20

Step 2: Select and Analyze Issue

For each bug issue, analyze:

Issue title and description
Steps to reproduce
Expected vs actual behavior
Related code files mentioned
Stack traces or error messages

Step 3: Create Fix Branch

# Create a branch for the fix
git checkout -b fix/issue-<number>-<short-description>

Step 4: Implement the Fix

Locate the relevant code files
Understand the root cause
Implement the minimal fix
Add or update tests
Run the test suite

Step 5: Create Pull Request

# Stage and commit changes
git add -A
git commit -m "fix: <description> (fixes #<issue-number>)"

# Push and create PR
git push -u origin fix/issue-<number>-<short-description>

gh pr create \
  --title "fix: <description>" \
  --body "## Summary
Fixes #<issue-number>

## Changes
- <change 1>
- <change 2>

## Testing
- [ ] Unit tests pass
- [ ] Manual testing completed

## Checklist
- [ ] Code follows project style
- [ ] Tests added/updated
- [ ] Documentation updated if needed"

Execution Instructions

When this skill is invoked, follow these steps:

1. Get Repository Info

gh repo view --json owner,name,defaultBranchRef

2. List Bug Issues

gh issue list --label "bug" --state open --json number,title,body,createdAt,url --limit 10

3. For Each Bug (or Selected Bug):

a) Read the issue details:

gh issue view <number> --json title,body,comments

b) Create a fix branch:

git checkout main
git pull origin main
git checkout -b fix/issue-<number>-<short-slug>

c) Analyze and implement:

Search codebase for related files
Read the relevant code
Understand the bug
Implement the fix
Write/update tests

d) Verify the fix:

# For Rust projects
cargo test
cargo clippy

# For Node projects
npm test
npm run lint

e) Commit and push:

git add -A
git commit -m "fix: <description>

Fixes #<issue-number>"
git push -u origin fix/issue-<number>-<short-slug>

f) Create the PR:

gh pr create --base main --title "fix: <title>" --body "<body>"

Issue Selection

If multiple bug issues exist, present them to the user:

Found N open bug issues:

1. #123 - Login fails with special characters
   Created: 2 days ago

2. #118 - API returns 500 on empty request
   Created: 5 days ago

3. #115 - Memory leak in worker process
   Created: 1 week ago

Which issue would you like to work on? (Enter number or 'all' for batch mode)

PR Template

Use this template for bug fix PRs:

## Summary

Fixes #<issue-number>

## Problem

<Brief description of the bug>

## Solution

<Description of the fix and why it works>

## Changes

- <File 1>: <What changed>
- <File 2>: <What changed>

## Testing

- [ ] Existing tests pass
- [ ] New tests added for the fix
- [ ] Manually verified the fix

## Screenshots/Logs

<If applicable, add before/after screenshots or log output>

Best Practices

Minimal Changes: Only fix the bug, don't refactor unrelated code
Add Tests: Every bug fix should include a test that would have caught it
Link Issues: Always reference the issue number in commits and PR
Verify First: Run tests before creating the PR
Clear Description: Explain the root cause and the fix

Troubleshooting

No bug issues found

# Check if label exists
gh label list | grep -i bug

# Create bug label if missing
gh label create bug --color d73a4a --description "Something isn't working"

Authentication issues

# Check gh auth status
gh auth status

# Re-authenticate if needed
gh auth login

Branch already exists

# Delete local branch and recreate
git branch -D fix/issue-<number>-<slug>
git checkout -b fix/issue-<number>-<slug>