Individual skill

repo-harness-ship

Close out verified harness work only when the user explicitly asks to commit, push, open a PR, merge, or clean merged worktrees.

assets/skill-commands/repo-harness-ship/SKILL.md

Read pinned source

Source commit f27ddc483e189f1bb81af6d9334cf3c5501a8349

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: No
Repository scan complete: No
Skill scan complete: Yes
Observed behavior: Not checked yet
Last checked: Nov 7, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings): 435
Repository last updated: Nov 8, 2026
License: MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

agentic-workflows Repository topic
ai-agents Repository topic
claude-code Repository topic
codegraph Repository topic
codex Repository topic
developer-tools Repository topic
typescript Repository topic
engineering Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

SKILL.mdcore · 1,428 bytes
agents/openai.yamlasset · 43 bytes
references/worker.mddoc · 4,128 bytes

Read excerpt


# repo-harness-ship

Bot entrypoint. Confirm the exact publication and cleanup authorization.
Assign Git/PR steps through `references/worker.md`. Consume the recorded checks,
revision and independent review when risk requires it. Preserve unrelated work.

Main publication, deletion, credentials/permissions and release/production
have separate boundaries. Merge only when this task authorizes main publication,
automated checks pass and GitHub has no change request or unresolved review thread
that a person started. A review bot thread is advisory.
An explicit no-merge instruction wins. Record the squash commit, its revert
command and the daily report after authorized publication.

The paragraph above is the internal PR flow. Classify each PR with the