generator-fix-worker

Stars13

Forks1

UpdatedMay 2, 2026 at 07:03

Internal Auto-Harness generator skill for one temporary fix bug batch in a dedicated worktree.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Source

redker56

redker56/auto-harness

View GitHub Repository View Creator Repositories

Download

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	generator-fix-worker
description	Internal Auto-Harness generator skill for one temporary fix bug batch in a dedicated worktree.
user-invocable	false

Generator Fix Worker

This skill governs a worktree-bound Generator fix worker.

At the start of this action, read these local harness artifacts from the worktree snapshot:

.harness-parallel/status.md
.harness-parallel/intake.md
.harness-parallel/spec.md
.harness-parallel/design-direction.md when the assigned bugs touch UX, layout, or interaction
.harness-parallel/contracts/sprint-XX-contract.md
.harness-parallel/contracts/sprint-XX-review.md when it exists for the current sprint
.harness-parallel/runtime.md
.harness-parallel/qa/sprint-XX-qa-report.md
.harness-parallel/qa/sprint-XX-retest.md when this cycle follows a failed retest

Then inspect the current project implementation relevant to this action:

Read the bug IDs and reproduction details the Orchestrator assigned first.
Read the files most likely to implement those bug surfaces before widening out to neighboring code.
Treat this worktree as isolated. Do not assume other worker changes already exist here unless they were merged into the base before the worktree was created.

Follow these rules:

Fix only the assigned bug cluster.
Keep edits tightly scoped to the files needed for the assigned bug IDs.
Do not modify .harness-parallel/ files.
Run targeted verification for your assigned bug IDs before finishing.
Make a local git commit in this worktree.
If a named fix cannot be completed without broad speculative changes, stop short of freelancing and report the blocker clearly.

More from this repository

same repository

evaluator-review-contract-parallel

redker56/auto-harness

Internal Auto-Harness evaluator skill for parallel sprint contract review before implementation. Use only inside the Evaluator subagent during review mode.

2026-05-0213

evaluator-write-final-parallel

redker56/auto-harness

Internal Auto-Harness evaluator skill for parallel final QA report aggregation. Use only inside the Evaluator subagent during evaluator_final_parallel.

2026-05-0213

evaluator-write-qa-parallel

redker56/auto-harness

Internal Auto-Harness evaluator skill for parallel sprint QA and QA report writing. Use only inside the Evaluator subagent during evaluator_qa_parallel.

2026-05-0213

evaluator-write-retest-parallel

redker56/auto-harness

Internal Auto-Harness evaluator skill for parallel sprint retest and retest report writing. Use only inside the Evaluator subagent during evaluator_retest_parallel.

2026-05-0213

generator-build-integrator

redker56/auto-harness

Internal Auto-Harness generator skill for worktree-merge build integration. Use only inside the parallel Generator integrator during build mode.

2026-05-0213

generator-build-worker

redker56/auto-harness

Internal Auto-Harness generator skill for one build dependency-graph node in a dedicated worktree.

2026-05-0213

name	generator-fix-worker
description	Internal Auto-Harness generator skill for one temporary fix bug batch in a dedicated worktree.
user-invocable	false

Generator Fix Worker

This skill governs a worktree-bound Generator fix worker.

At the start of this action, read these local harness artifacts from the worktree snapshot:

.harness-parallel/status.md
.harness-parallel/intake.md
.harness-parallel/spec.md
.harness-parallel/design-direction.md when the assigned bugs touch UX, layout, or interaction
.harness-parallel/contracts/sprint-XX-contract.md
.harness-parallel/contracts/sprint-XX-review.md when it exists for the current sprint
.harness-parallel/runtime.md
.harness-parallel/qa/sprint-XX-qa-report.md
.harness-parallel/qa/sprint-XX-retest.md when this cycle follows a failed retest

Then inspect the current project implementation relevant to this action:

Read the bug IDs and reproduction details the Orchestrator assigned first.
Read the files most likely to implement those bug surfaces before widening out to neighboring code.
Treat this worktree as isolated. Do not assume other worker changes already exist here unless they were merged into the base before the worktree was created.

Follow these rules:

Fix only the assigned bug cluster.
Keep edits tightly scoped to the files needed for the assigned bug IDs.
Do not modify .harness-parallel/ files.
Run targeted verification for your assigned bug IDs before finishing.
Make a local git commit in this worktree.
If a named fix cannot be completed without broad speculative changes, stop short of freelancing and report the blocker clearly.