Skip to content
Skills Library
Programming · Building & coding

worker

/worker

Work one rig ticket as a worker agent. Read the ticket, implement it in the assigned worktree, report to the manager, and hand it off for review. Use it when your prompt says you are the rig worker for a ticket.

Repository
herdr-rig ↗
Licence
MIT
Last repository change
11.11.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 11.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Work one rig ticket as a worker agent. Read the ticket, implement it in the assigned worktree, report to the manager, and hand it off for review. Use it when your prompt says you are the rig worker for a ticket.

Original author description

Work one rig ticket as a worker agent. Read the ticket, implement it in the assigned worktree, report to the manager, and hand it off for review. Use it when your prompt says you are the rig worker for a ticket.

How it works

  1. Start
  2. Work
  3. Finish
  4. Never
Original SKILL.md headings · 28 lines, 291 words
SKILL.md preview
---
name: worker
description: Work one rig ticket as a worker agent. Read the ticket, implement it in the assigned worktree, report to the manager, and hand it off for review. Use it when your prompt says you are the rig worker for a ticket.
---

# rig worker

You own **one ticket**. A manager session dispatched you, and you report to it with the `rig` CLI.

## Start
1. `rig show <T>` prints the goal, acceptance, verify, scope, earlier messages and runs. If earlier runs exist, you are resuming: check `git log` and `git status` first and continue from there. Don't start over.
2. Work only in your current directory, which is the ticket's worktree. Don't touch sibling worktrees or the main checkout.

## Work
- Plan briefly, then make small, focused commits with clear messages.
- Stay inside the scope. If the right fix needs to go further, say so: `rig say manager "scope: need to touch X because Y — ok?"`.
- Check `rig inbox` between steps. A manager message, or anything typed into your session that starts with `[rig]`, overrides your plan.
- When blocked, ask with options and a default: `rig say manager "Q: A or B? I'll go with A in 5 min if no answer"`. Then keep working on whatever doesn't depend on the answer.
- At real milestones, send one line: `rig say manager "milestone: parser done, tests next"`. Don't send chatter.

## Finish
1. Run every **Verify** command and read the output. Fix failures, don't explain them away.
2. Commit everything. `git status` must be clean.
3. `rig edit <T> status=review`
4. `rig say manager "done: <what changed>; verify: <commands + pass/fail>; risks: <any>"`

If you can't finish, set `rig edit <T> status=blocked` and use `rig say manager` to explain exactly what is in the way and what you tried.

## Never
- Don't push, merge into the base branch, or rewrite history outside your branch.
- Don't fake a verify or skip tests to get to green.

Versions

The database has no other skills named worker.

Database snapshot: 13.11.2026 · package version c5ee9f262a38 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 86reviewer
    Review one rig ticket's branch against its brief and send a PASS or FIX verdict to the manager. Use it when your prompt says you are the rig reviewer for a ticket.
  • 90implement
    Build one approved piece of work from its spec or ticket, prove the result, and self-review it. Use when the user asks to implement a ticket, a spec slice or an agreed change, or when a coordinator briefs a worker to build one ticket.
  • 100ticket
    Open the logbook issue of a piece of work and have a subagent do it in a worktree and a branch of its own, under the supervision of the current session. Use when a feature, a fix or any change is asked, when something is left to do that would have been a TODO (it becomes an…
  • 100code-implement
    Work one ticket from start to PR: read its acceptance criteria, branch, build them test-first with parallel build workers, and commit after each. Then open the PR with h2xd:git-pr-body, review it with h2xd:review-pr and fix the threads with h2xd:review-fix, without stopping…
  • 100work
    Take one ticket from intake to a reviewed, verified branch — plan it, implement it in its own worktree, prove its tests, have a cold-context agent review it, fix what the review finds and have the fixes reviewed once. Use when the user runs /10x:work with a GitHub issue, a…
  • 100worktree
    Use when taking one ticket or a related ticket group into its own branch and git worktree for implementation.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.