fabrik-implement-comment

Applies user-requested code changes during Fabrik's Implement stage and commits the result.

22|Updated Apr 1, 2026
One-click install
npx skills add https://github.com/handarbeit/fabrik --skill fabrik-implement-comment-handarbeit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fabrik-implement-comment
Source: https://github.com/handarbeit/fabrik/tree/main/plugin/fabrik-workflows/skills/fabrik-implement-comment
Command: npx skills add https://github.com/handarbeit/fabrik --skill fabrik-implement-comment-handarbeit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a user comments on a GitHub issue mid-implementation, someone must interpret the feedback, apply the code change, verify it compiles and passes tests, commit and push, and update the task checklist — all without prematurely advancing the automated pipeline. This Skill guides Claude Code through exactly that comment-review loop inside the Fabrik Implement stage. ## Core Features & Use Cases - Scoped change application: Reads .fabrik-context/issue.md and .fabrik-context/stage-Plan.md to understand the spec and current plan state, then makes only the minimal change the user requested. - Safe verification discipline: Enforces foreground, timeout-bounded verification (build commands, framework test timeouts) instead of backgrounding dev servers or CI waits that would orphan processes or silently end the stage. - Checklist and label management: Updates the Plan stage comment's task checkboxes via gh issue view, respects labels like fabrik:extend-turns and fabrik:tools-denied, and never emits FABRIK_STAGE_COMPLETE so the pipeline does not advance. - Use Case: A user comments "use the interface type instead of the concrete struct" on an in-progress issue; the Skill applies the change, runs the tests, commits with a message referencing the feedback, updates the plan checklist, and returns control to the engine. ## Quick Start Ask the agent to act as the Fabrik Implement comment reviewer and apply the user's latest comment on the current issue, then commit and push the change without signaling stage completion.

Frequently Asked Questions about fabrik-implement-comment

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

FAQPage Schema
How do I handle user feedback comments during an automated implementation stage?

Read the issue body and plan stage output from .fabrik-context, apply the minimal requested change, verify compilation and tests, then commit and push with a message referencing the feedback. Do not signal stage completion; the pipeline continues after the comment is processed.

How do I update a GitHub issue task checklist from the command line?

Use gh issue view with --json comments and a jq filter to find the Plan stage comment's databaseId by its prefix, then edit the relevant checkbox in that comment body. The Skill targets comments starting with the Fabrik stage header.

Why can't I background a dev server to verify changes in a headless stage?

Backgrounded processes detach via setsid and outlive the stage, becoming orphaned processes holding ports because the engine's teardown kill is process-group scoped. Use one-shot builds, timeout-bounded commands, or foreground test runs with framework timeout flags instead.

What happens when the comment-processing turn limit is reached?

The turn budget is a time-slicer, not a failure: the engine preserves the work and the next invocation resumes the same session. Commit incremental progress rather than trying to finish everything in one slice.

Can I post stage output directly with gh issue comment or gh pr comment?

No. Direct comment creation bypasses the engine's formatting, produces duplicates, and triggers a self-review loop. Write output to stdout only; resolving PR review threads via the GraphQL resolveReviewThread mutation is the permitted exception.