Skip to content
Back to skills

Generator Build Worker

ASecurity

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

  • 14 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added May 26, 2026
ai-agentsgonodegit

Security analysis

A100/100

Scanned May 27, 2026

npx -y skills add redker56/auto-harness --skill generator-build-worker --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Generator Build Worker?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Generator Build Worker
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/redker56-generator-build-worker/badge)](https://www.skillsdirectory.com/skills/redker56-generator-build-worker)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: generator-build-worker
description: Internal Auto-Harness generator skill for one build dependency-graph node in a dedicated worktree.
user-invocable: false
---

# Generator Build Worker

This skill governs a worktree-bound Generator **build 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`
- `.harness-parallel/contracts/sprint-XX-contract.md`
- `.harness-parallel/contracts/sprint-XX-review.md` when it exists for the current sprint

Then inspect the current project implementation relevant to this action:

- Read the assigned owned files or globs first.
- Read neighboring files only as dependency context unless the Orchestrator explicitly assigned them to you.
- 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:

- Implement only the assigned dependency-graph node.
- Modify only the owned files or globs named by the Orchestrator.
- Do not modify `.harness-parallel/` files.
- Run targeted verification for your node before finishing.
- Make a local git commit in this worktree.
- If your task cannot be completed without touching an unowned path, stop short of freelancing and report the blocker clearly.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.