skills.rest
Chulf58
Chulf58COMMUNITY
Explore all skills by this author →
GitHub

forge:debug

Run the FORGE debug pipeline to analyze bugs and generate fix plans.

1|Updated Apr 14, 2026
Search Tags:#automation#workflow#debugging#worktree#gate#reviewers#FORGE
One-click install
npx skills add https://github.com/Chulf58/FORGE --skill forge-debug
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: forge:debug
Source: https://github.com/Chulf58/FORGE/tree/main/skills/debug
Command: npx skills add https://github.com/Chulf58/FORGE --skill forge-debug

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the end-to-end debugging workflow by running the FORGE debug pipeline when a bug, broken feature, or failing tests are reported, making the investigation observable and auditable.

Core Features & Use Cases

  • Orchestrates a dedicated debug run with a unique runId and a worktree that isolates the debugging session.
  • Dispatches the appropriate reviewers and manages gate transitions to ensure human approval before applying fixes.
  • Supports typical debugging scenarios such as flaky tests, regression bugs, and environment-specific failures with clear handoffs and traceability.

Quick Start

Describe the bug succinctly and run /forge:debug to start tracing and implementing a fix.

Frequently Asked Questions about forge:debug

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

FAQPage Schema
How do I automate debugging workflows for failing tests and regression bugs?▼

Automated debugging workflows run a deterministic pipeline that creates a unique run, sets up an isolated worktree, dispatches reviewers, and enforces gate approvals before applying fixes to failing tests or regression bugs.

What is a gate-based approval process for debugging pipelines?▼

A gate-based approval process manages run status transitions by requiring human reviewer dispatch and explicit approval at designated gates, ensuring fixes are audited and traceable before being applied to the isolated worktree.

How do I isolate a debugging session to investigate environment-specific failures?▼

Isolating a debugging session requires creating a dedicated worktree that maintains a separate workspace for the run, preventing interference while investigating environment-specific failures or flaky tests.

Can I enforce required inputs before starting an automated debug run?▼

Enforcing required inputs is supported before run creation, ensuring the pipeline validates essential bug report details or failing test data prior to generating a unique runId and dispatching reviewers.

What is the best way to coordinate reviewer dispatch during bug investigation?▼

Coordinating reviewer dispatch is handled automatically within the debug pipeline, routing the investigation to appropriate reviewers and pausing at gate2 to output a clear fix plan for human review.

Does the FORGE debug pipeline support traceability for flaky test investigations?▼

The FORGE debug pipeline supports traceability for flaky test investigations by maintaining run status updates, unique runIds, and dedicated worktrees, making the entire debugging workflow observable and auditable.

Related Skills

Explore More Software Engineering Skills→
gajjalaashok75-UIgajjalaashok75-UI
2

e2e-testing-patterns

Designs Playwright and Cypress end-to-end test suites for critical user journeys.

Community
Advanced
hanzlahabibhanzlahabib
2

rcode-prove-it

Write failing tests before implementing JavaScript and TypeScript fixes.

Community
Intermediate
sambeausambeau
5

kanbanzai-workflow

Enforce lifecycle gates and stage transitions for Kanbanzai features and tasks.

Community
Advanced
lestrratlestrrat
2

test-fix-loop

Continuously find and fix failing Go tests in a worktree.

Community
Advanced