generator-apply-fixes

Stars13

Forks1

UpdatedApril 6, 2026 at 02:10

Internal Auto-Harness generator skill for QA fix cycles. Use only inside the Generator subagent when it is addressing named defects from QA or retest.

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 Quality Assurance Analysts and TestersComputer and Mathematical Occupations·SOC 15-1253

File Explorer

4 files

SKILL.md

readonly

name	generator-apply-fixes
description	Internal Auto-Harness generator skill for QA fix cycles. Use only inside the Generator subagent when it is addressing named defects from QA or retest.
user-invocable	false

Generator Apply Fixes

This skill governs Generator fix mode.

At the start of this action, read these harness artifacts from the project:

.harness/status.md
.harness/intake.md
.harness/spec.md
.harness/design-direction.md when the named defects touch UX, layout, or interaction rules.
.harness/contracts/sprint-XX-contract.md
.harness/contracts/sprint-XX-review.md when it exists for the current sprint.
.harness/runtime.md
.harness/qa/sprint-XX-qa-report.md
.harness/qa/sprint-XX-retest.md when the current fix cycle follows a failed retest.
.harness/qa/sprint-XX-fix-log.md when revising the current sprint fix log.

Then inspect the current project implementation relevant to this action:

Read the source files, routes, components, services, tests, and config touched by the named defects and the necessary regression surface around them.
Use code and runtime evidence to scope fixes precisely instead of broad cleanup.

Then read these skill references:

references/protocols/file-ownership.md
references/templates/fix-log.md
references/templates/runtime-template.md

Follow these rules:

Fix only defects named in the current QA or retest context unless a tightly related adjustment is required.
Treat the current sprint review, when present, as implementation guidance and cautions that still apply during the fix cycle.
Update the runtime contract when startup, access, or healthcheck behavior changed.
Record the actual fixes in the sprint fix log.
Keep the fix log tied to named defects, changed files, and any verification notes that matter for retest.
Do not rewrite QA or retest artifacts yourself.

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-apply-fixes
description	Internal Auto-Harness generator skill for QA fix cycles. Use only inside the Generator subagent when it is addressing named defects from QA or retest.
user-invocable	false

Generator Apply Fixes

This skill governs Generator fix mode.

At the start of this action, read these harness artifacts from the project:

.harness/status.md
.harness/intake.md
.harness/spec.md
.harness/design-direction.md when the named defects touch UX, layout, or interaction rules.
.harness/contracts/sprint-XX-contract.md
.harness/contracts/sprint-XX-review.md when it exists for the current sprint.
.harness/runtime.md
.harness/qa/sprint-XX-qa-report.md
.harness/qa/sprint-XX-retest.md when the current fix cycle follows a failed retest.
.harness/qa/sprint-XX-fix-log.md when revising the current sprint fix log.

Then inspect the current project implementation relevant to this action:

Read the source files, routes, components, services, tests, and config touched by the named defects and the necessary regression surface around them.
Use code and runtime evidence to scope fixes precisely instead of broad cleanup.

Then read these skill references:

references/protocols/file-ownership.md
references/templates/fix-log.md
references/templates/runtime-template.md

Follow these rules:

Fix only defects named in the current QA or retest context unless a tightly related adjustment is required.
Treat the current sprint review, when present, as implementation guidance and cautions that still apply during the fix cycle.
Update the runtime contract when startup, access, or healthcheck behavior changed.
Record the actual fixes in the sprint fix log.
Keep the fix log tied to named defects, changed files, and any verification notes that matter for retest.
Do not rewrite QA or retest artifacts yourself.