fix-bug
/fix-bug
Use when given a GitHub issue URL or number to investigate and implement a fix. Triggers on "fix issue", "fix bug", "fix #123", GitHub issue URLs, or any request to resolve a reported problem from a GitHub issue. Also triggers when asked to investigate errors, diagnose failures, or debug unexpected behavior in DBHub.
- Author
- bytebase ↗
- Repository
- dbhub ↗
- Licence
- MIT
- Last repository change
- 26.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 2
No signals detected. Repository changed on 26.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Use when given a GitHub issue URL or number to investigate and implement a fix. Triggers on "fix issue", "fix bug", "fix #123", GitHub issue URLs, or any request to resolve a reported problem from a GitHub issue. Also triggers when asked to investigate errors, diagnose failures, or debug unexpected behavior in DBHub.
Triggers from the description
Original author description
Use when given a GitHub issue URL or number to investigate and implement a fix. Triggers on "fix issue", "fix bug", "fix #123", GitHub issue URLs, or any request to resolve a reported problem from a GitHub issue. Also triggers when asked to investigate errors, diagnose failures, or debug unexpected behavior in DBHub.
How it works
- Workflow
- Step 1: Fetch Issue
- Step 2: Analyze Issue
- Step 3: Locate Relevant Code
- Step 4: Reproduce
- Step 5: Plan the Fix
- Step 6: Implement
- Step 7: Verify
- Step 8: Create PR
- Common Mistakes
SKILL.md preview
---
name: fix-bug
description: Use when given a GitHub issue URL or number to investigate and implement a fix. Triggers on "fix issue", "fix bug", "fix #123", GitHub issue URLs, or any request to resolve a reported problem from a GitHub issue. Also triggers when asked to investigate errors, diagnose failures, or debug unexpected behavior in DBHub.
---
# Fix Bug from GitHub Issue
Systematic workflow for turning a GitHub issue into a working fix in the DBHub codebase.
## Workflow
1. **Fetch** → 2. **Analyze** → 3. **Locate** → 4. **Reproduce** → 5. **Plan** → 6. **Implement** → 7. **Verify** → 8. **PR**
## Step 1: Fetch Issue
```bash
# From URL: https://github.com/owner/repo/issues/123
gh issue view 123 --json title,body,labels,comments,state
# From another repo
gh issue view 123 --repo owner/repo --json title,body,labels,comments,state
```
| Input | How to fetch |
|-------|-------------|
| `https://github.com/owner/repo/issues/42` | `gh issue view 42 --repo owner/repo` |
| `#42` or `42` | `gh issue view 42` (current repo) |
| `owner/repo#42` | `gh issue view 42 --repo owner/repo` |
## Step 2: Analyze Issue
Extract from the issue:
- **What's broken**: Expected vs actual behavior
- **Reproduction steps**: How to trigger the bug
- **Environment**: Database type, connection method (DSN, SSH tunnel, TOML config), transport (stdio/HTTP)
- **Labels/comments**: May reveal affected area or prior investigation
- **Linked PRs/issues**: Check for related context
## Step 3: Locate Relevant Code
Use the issue details to identify which part of the codebase is affected. DBHub has a clear modular structure — most bugs fall into one of these areas:
| Bug Category | Where to Look | Key Files |
|-------------|--------------|-----------|
| Connection failures | Connector implementations | `src/connectors/{db-type}/index.ts`, `src/connectors/manager.ts` |
| SQL execution errors | Tool handlers | `src/tools/execute-sql.ts`, `src/utils/allowed-keywords.ts` |
| Schema/table listing | Search tool | `src/tools/search-objects.ts` |
| DSN parsing issues | Parser logic | `src/connectors/{db-type}/index.ts` (DSNParser), `src/utils/dsn-obfuscate.ts`, `src/utils/safe-url.ts` |
| SSH tunnel problems | Tunnel utilities | `src/utils/ssh-tunnel.ts`, `src/utils/ssh-config-parser.ts` |
| TOML config issues | Config loading | `src/config/toml-loader.ts`, `src/types/config.ts` |
| Multi-database routing | Manager & tools | `src/connectors/manager.ts`, `src/utils/tool-handler-helpers.ts` |
| Custom tool issues | Custom handler | `src/tools/custom-tool-handler.ts`, `src/tools/registry.ts` |
| HTTP transport | Server setup | `src/server.ts` |
| Read-only violations | SQL validation | `src/utils/allowed-keywords.ts`, `src/utils/sql-parser.ts` |
| Row limiting | SQL rewriting | `src/utils/sql-row-limiter.ts` |
| API endpoint issues | API handlers | `src/api/sources.ts`, `src/api/requests.ts` |
| AWS IAM auth | Token signing | `src/utils/aws-rds-signer.ts` |
Search for error messages, function names, or file paths mentioned in the issue. Trace the code path from entry point to the failure.
## Step 4: Reproduce
**If integration tests exist for the area:**
Write a failing test that captures the bug. DBHub's test infrastructure makes this straightforward:
- Database connector bugs → extend existing integration test in `src/connectors/__tests__/`
- Utility bugs → add cases to existing unit tests in `src/utils/__tests__/`
- Tool handler bugs → add to `src/tools/__tests__/`
- Config bugs → add to `src/config/__tests__/`
Use the test fixtures in `src/__fixtures__/` for multi-database or readonly/max_rows scenarios.
**If no test infrastructure applies:**
Trace the code path and confirm the logic flaw by reading.
## Step 5: Plan the Fix
For non-trivial fixes (multi-file, architectural impact): use `EnterPlanMode`.
For simple fixes (single function, clear root cause): proceed directly.
## Step 6: Implement
- Fix the root cause, not just the symptom
- Keep changes minimal and focused
- Follow existing code conventions (see CLAUDE.md for style guide)
- Use parameterized queries for any database operations
- Validate inputs with zod schemas where appropriate
## Step 7: Verify
Run the relevant tests to confirm the fix:
```bash
pnpm test:unit # Quick check — no Docker needed
pnpm test src/path/to/test.ts # Run the specific test file
pnpm test:integration # Full integration suite if needed
```
Check that:
- The failing test (if written) now passes
- No existing tests regressed
- The diff fully addresses the issue
## Step 8: Create PR
1. **Create a branch**:
```bash
git checkout -b fix/issue-123
```
2. **Commit changes** referencing the issue:
```bash
git add <changed-files>
git commit -m "$(cat <<'EOF'
Fix: <short description>
Closes #123
EOF
)"
```
3. **Push and create the PR**:
```bash
git push -u origin fix/issue-123
gh pr create --title "Fix: <short description>" --body "$(cat <<'EOF'
## Summary
<What was broken and how this fixes it>
## Changes
<Bullet list of changes>
Closes #123
## Test plan
- [ ] Existing tests pass
- [ ] New test covers the bug scenario (if applicable)
EOF
)"
```
4. **Return the PR URL** to the user.
## Common Mistakes
- **Fixing symptoms instead of root cause**: Trace the full code path before patching
- **Skipping reproduction**: A fix without a repro is a guess
- **Scope creep**: Fix the reported issue, don't refactor surrounding code
- **Missing edge cases**: Check if the fix handles related scenarios mentioned in comments
- **Not testing with the right database**: If the bug is database-specific, test with that connector
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · bytebase/dbhub | 100 | MIT |
| mthines/agent-skills | 100 | MIT |
| mgiovani/cc-arsenal | 100 | MIT |
| tddworks/claudebar | 100 | Apache-2.0 |
| remix-run/react-router | 100 | MIT |
| Cynnamoroll/factory-stack | 100 | MIT |
| nowsprinting/unity-coding-skills | 100 | Unlicense |
| Slama-Consulting/proofbench | 100 | MIT |
| downbelowdotxyz/downbelow-skills | 100 | MIT |
Database snapshot: 13.11.2026 · package version c9e25acde758 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100bugfix
Fix a bug from a GitHub issue, following the reproduce-first workflow. Use when the user asks to fix a bug, investigate a GitHub issue, or debug a user-reported problem. Takes a GitHub issue URL or number as input. - 100fix-issue
Analyze and fix a GitHub issue for the iam-policy-validator project. Use when the user wants to fix a GitHub issue, resolve a bug report, or implement a feature request from an issue. Triggers on "/fix-issue", "fix issue #42", "resolve this GitHub issue", or "work on issue". - 90fix-issue
Resolve a GitHub issue end to end, from reading the issue through to opening a pull request. Use when the user names an issue number to fix. - 88fix-github-issue
Fix a GitHub issue by number. Use when asked to fix GitHub issues. - 90triage-issue
Triage a bug or issue by exploring the codebase to find root cause, then create a GitHub issue with a TDD-based fix plan. Use when user reports a bug, wants to file an issue, mentions "triage", or wants to investigate and plan a fix for a problem. - 100reproduce-bug
Systematically reproduce and investigate a bug from a GitHub issue. Use when the user provides a GitHub issue number or URL for a bug they want reproduced or investigated.