skills.rest
Hoang604
Hoang604COMMUNITY
Explore all skills by this author →
GitHub

d-execute

Execute bug-fix tasks from FIX_PLAN.md and generate FIX_SUMMARY.md.

Updated Jan 22, 2026
Search Tags:#automation#workflow#debugging#summary#bug-fix
One-click install
npx skills add https://github.com/Hoang604/get-thing-done --skill d-execute
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: d-execute
Source: https://github.com/Hoang604/get-thing-done/tree/main/.claude/skills/d-execute
Command: npx skills add https://github.com/Hoang604/get-thing-done --skill d-execute

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the end-to-end bug-fix workflow by reading a fix plan, executing tasks deterministically, validating outcomes after each step, and producing a concise summary of changes.

Core Features & Use Cases

  • Load and interpret FIX_PLAN.md to drive a structured bug-fix workflow.
  • Execute each task atomically with verification before proceeding and log deviations for later review.
  • Generate FIX_SUMMARY.md documenting applied changes, rationale, and recommended next steps.

Quick Start

Place a FIX_PLAN.md in the GTD debug directory and the skill will execute tasks in order and generate FIX_SUMMARY.md.

Frequently Asked Questions about d-execute

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

FAQPage Schema
How do I automate executing a bug-fix plan from a markdown file?▼

Automating a bug-fix plan requires placing a FIX_PLAN.md in the GTD debug directory. The tool reads the plan, executes tasks deterministically, validates outcomes after each step, and produces a FIX_SUMMARY.md.

How does atomic state change verification work during code debugging?▼

Atomic state changes during debugging apply each task independently and verify the outcome before proceeding. This structured workflow logs any deviations encountered during execution for later review.

Do I need a specific file format to start the automated bug-fix workflow?▼

Yes, the automated bug-fix workflow requires a FIX_PLAN.md file. You must place this file in the GTD debug directory to enable the tool to read and execute the tasks in order.

Can I generate a summary of applied code changes and rationale automatically?▼

Yes, generating a summary of applied code changes is automated. The workflow outputs a FIX_SUMMARY.md that documents the applied changes, the rationale behind them, and recommended next steps.

What is the best way to handle workflow deviations when applying bug fixes?▼

Handling workflow deviations involves executing tasks atomically and logging deviations during the bug-fix process. This ensures any issues encountered during state changes are recorded for later review.

Why does my automated bug-fix execution stop before completing all tasks?▼

Automated bug-fix execution stops if a verification step fails after an atomic state change. The workflow validates outcomes before proceeding and logs deviations to ensure code stability.

Related Skills

Explore More Software Engineering Skills→
VeronikaVashkevichVeronikaVashkevich

aif-fix

Diagnose codebase bugs and generate a FIX_PLAN.md for guided fixes.

Community
Advanced
mrp4stenmrp4sten
3

pr-review

Fetch GitHub pull request metadata and diffs, then categorize findings by severity.

Community
Advanced
gileckgileck

full-project-audit

Audit repository deviations from guidelines and architecture rules without code changes.

Community
Advanced
Pryma-TechPryma-Tech

verify

Verify code changes by running tests and reporting pass/fail evidence.

Community
Intermediate