workflow-architect-bug-fixer

Audit code across seven dimensions and apply user-approved fixes with verification.

65|8|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/EasyCode-Obsidian/workflow-architect --skill workflow-architect-bug-fixer
Or copy as Structured Prompt for Agentβ–Ό
Please help me install this Agent Skill.
Skill: workflow-architect-bug-fixer
Source: https://github.com/EasyCode-Obsidian/workflow-architect/tree/main/claude/skills/workflow-architect-bug-fixer
Command: npx skills add https://github.com/EasyCode-Obsidian/workflow-architect --skill workflow-architect-bug-fixer

SYSTEM DOCUMENTATION & REQUIREMENTS

πŸ’‘ This Skill includes references (resource) components.

What problem does it solve?

It helps you perform reliable code audits and targeted bug fixes by running a structured 7-dimension review and verifying changes, reducing the chance of hidden defects and regression.

Core Features & Use Cases

  • Seven-dimension code audit: Reviews security, logic errors, concurrency issues, performance problems, error handling, dependency risks, and consistency issues with severity classification.
  • Two execution modes: Runs standalone for an arbitrary file/directory/bug description, or integrated with workflow-architect Phase 4 using the stored execution context.
  • User-confirmed, verification-first fixes: Prevents silent changes by showing findings first, applying only approved fixes, and always running targeted verification after each change.
  • Fix loop with controlled escalation: Uses a reproduce β†’ root-cause β†’ fix-design β†’ implement β†’ verify cycle, including revert-and-ask if verification fails.

Quick Start

Use the workflow-architect-bug-fixer skill to review and fix bugs in the directory you specify by passing it as the target argument.

Frequently Asked Questions about workflow-architect-bug-fixer

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

FAQPage Schema
How do I perform a systematic code review to find logic errors and concurrency issues?β–Ό

To prevent regression during bug fixing, implement a reproduce, root-cause, fix-design, implement, and verify loop. Require user approval before applying changes and run targeted verification after each fix to ensure stability.

How do I fix code bugs without causing regression in existing functionality?β–Ό

To prevent regression during bug fixing, implement a reproduce, root-cause, fix-design, implement, and verify loop. Require user approval before applying changes and run targeted verification after each fix to ensure stability.

What is the best way to run a security audit and dependency risk check on my source files?β–Ό

Standalone code audits accept arbitrary file paths, directories, or bug descriptions as input arguments. They execute a structured seven-dimension review without requiring an active workflow, isolating defects in deliverable code paths.

Can I run a standalone code audit on a specific directory without an active workflow?β–Ό

Standalone code audits accept arbitrary file paths, directories, or bug descriptions as input arguments. They execute a structured seven-dimension review without requiring an active workflow, isolating defects in deliverable code paths.

What happens if verification fails after applying a code fix?β–Ό

If verification fails after a code fix, the execution loop triggers a controlled escalation, reverting the changes and prompting the user for guidance. This ensures only verified modifications persist in the codebase.