smith-bugfix

Automate end-to-end bug fixes from invocation to merged PR.

50|8|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/ATTCKDigital/smith --skill smith-bugfix
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: smith-bugfix
Source: https://github.com/ATTCKDigital/smith/tree/main/skills/smith-bugfix
Command: npx skills add https://github.com/ATTCKDigital/smith --skill smith-bugfix

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates end-to-end bug fixes from invocation to merged PR, eliminating manual handoffs and gatekeeping.

Core Features & Use Cases

  • Autonomous end-to-end bug fixes: from invocation through to a merged PR for small changes that do not require a formal spec.
  • Deterministic worktree and audit log: per-branch vault logging, branch tracking, and automated tests and PR creation.
  • Safe, autonomous operation: isolates the worktree from the user’s current branch with clear recovery steps if something goes wrong.

Quick Start

Describe the bug and let the bugfix workflow automatically handle branch creation, code changes, tests, and PR.

Frequently Asked Questions about smith-bugfix

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate bug fixes from a trigger to a merged PR?

To automate autonomous bug fixes end-to-end, invoke the workflow with a bug description. It handles branch creation, code changes, tests, and PR opening automatically for small, well-scoped changes.

When should I use autonomous bugfix workflows instead of manual git fixes?

Autonomous bugfix workflows are ideal for small, well-scoped bugs involving 1–3 files that do not require formal requirements or extensive planning, eliminating manual handoffs and gatekeeping.

How does git worktree isolation work for automated bug fixes?

Git worktree isolation creates a per-branch worktree from origin/main, keeping your current branch safe. It logs to a vault and provides clear recovery steps if the automated fix process encounters issues.

What are the limitations of using an autonomous bugfix workflow?

Autonomous bugfix workflows are limited to minor changes and small bugs involving 1–3 files. They are not suited for complex changes requiring formal specifications, extensive planning, or multi-file architectural modifications.

Can I run automated tests and PR management together for minor code changes?

Yes, automated tests and PR management run together in deterministic phases. The workflow executes setup, fix, tests, review, and merge phases sequentially, opening a PR with an auditable history log.

Do I need formal requirements to run an automated PR bugfix workflow?

No, you do not need formal requirements. The automated PR bugfix workflow is designed specifically for minor changes and well-scoped bugs that bypass extensive planning and formal specification requirements.