verifybug
Verify bug fix by running validate target and confirming fix
What this skill does
# Verify Bug Fix
Verifies that a beads bug is fixed by:
1. Checking acceptance criteria (reproduction steps and fix verification)
2. Executing the build system `validate` target
3. Confirming the bug no longer reproduces
## Usage
```bash
# Verify bug fix
/bkff:verifybug --issue=beads-abc123
# Output as JSON
/bkff:verifybug --issue=beads-abc123 --format=json
```
## Verification Process
1. **Acceptance Criteria Check**: Bug must have:
- Reproduction steps (how to trigger the bug)
- Fix verification steps (how to confirm the fix)
2. **Validate Target**: Runs tests to ensure:
- The bug no longer reproduces
- No regression in existing functionality
- Code quality standards maintained
## What Gets Checked
The `validate` target for bugs should verify:
| Check Type | Description |
|------------|-------------|
| Regression Tests | Bug-specific regression test passes |
| Unit Tests | All related unit tests pass |
| Quality | No new quality issues introduced |
| Standards | Fix follows coding standards |
## Output
### Verification Passed
```
Info: Verifying bug fix: beads-abc123
Verification Result
─────────────────────────────────────
Issue: beads-abc123
Target: validate
✓ Verification passed
```
### Verification Failed
```
Info: Verifying bug fix: beads-abc123
Verification Result
─────────────────────────────────────
Issue: beads-abc123
Target: validate
✗ Verification failed
Summary:
• Tests failed: 1
Failures:
tests/test-regression.sh:-: [test] Test failed: test_bug_123_does_not_reproduce
```
## Bug Issue Best Practices
For effective bug verification, ensure your bug issue includes:
```markdown
## Description
Clear description of the bug behavior.
## Reproduction Steps
1. Step to reproduce
2. Step to reproduce
3. Observe the bug
## Expected Behavior
What should happen instead.
## Fix Verification
1. Step to verify fix
2. Confirm expected behavior
3. Check no regression
```
## Requirements
- Beads bug must have acceptance criteria (reproduction/verification steps)
- Build system must have a `validate` target in Makefile
- `bd` CLI must be available
## Exit Codes
- `0` - Verification passed (bug is fixed)
- `1` - Verification failed (bug still reproduces or other failures)
- `2` - Missing acceptance criteria
- `3` - Missing validate target
## Related Skills
- `/bkff:verifytask` - Verify task completion
- `/bkff:verifyfeat` - Verify feature completion
## Implementation
```bash
#!/usr/bin/env bash
set -euo pipefail
SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
PLUGIN_DIR="$(dirname "$(dirname "$SCRIPT_DIR")")"
source "$PLUGIN_DIR/lib/common.sh"
source "$PLUGIN_DIR/lib/verification.sh"
# Parse arguments
issue_id=""
format="human"
for arg in "$@"; do
case "$arg" in
--issue=*) issue_id="${arg#--issue=}" ;;
--format=json) format="json" ;;
--format=human) format="human" ;;
--json) format="json" ;;
esac
done
# Validate prerequisites
require_worktree
require_bd
if [[ -z "$issue_id" ]]; then
error_exit "Issue ID required. Use --issue=<id>"
fi
# Run verification
result=$(verify_bug "$issue_id")
# Output based on format
if [[ "$format" == "json" ]]; then
echo "$result"
else
echo "$result" | print_verification_result
fi
# Exit with appropriate code
status=$(echo "$result" | jq -r '.status')
[[ "$status" == "pass" ]]
```
Related in Code Review
gstack
IncludedFast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)
startup-due-diligence
IncludedLegal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.
interview-master
IncludedThis skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.
fix-issue
IncludedFixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.
sf-apex
IncludedGenerates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.
swift-development
IncludedComprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.