About repo-delivery
repo-delivery is a skill for controlled Git delivery, intended for workflows that need authorized commits, pushes, or integrations. It requires a precise target and mutation scope, and reports outcomes bounded by available evidence.
Key features
- 01Validate repository, branch, and authorization
- 02Route commits, pushes, and integrations by task
- 03Limit staging and preserve unrelated changes
- 04Report local and remote outcomes separately
Use cases
- 01Create a local commit for completed changes
- 02Sync or integrate an authorized branch
- 03Normalize checkpoints or resolve conflicts
- 04Prepare an evidence-bounded delivery report
Install
Copy the command and run it in a terminal.
npx skills add https:/After installing, type/repo-deliveryin Claude Code to confirm it loaded.
Bundled files
References and scripts installed along with SKILL.md.
agents/openai.yamlreferences/checklist.mddelivery-report.mdeval-cases.mdexecution-durability.mdhistory-normalization.mdresolving-merge-conflicts.mdskills-release.mdusage.mdDetails
From the project READMERepository Delivery
Entry Gate
Own authorized Git mutation only. Require exact target repository/branch, mutation scope, reviewed basis, and any required destination authorization; preserve unrelated Worktree changes and stop on ambiguous scope or failed preflight.
Route Map
| Request condition | Read | Result |
|---|---|---|
| Commit, push, sync, integration, cleanup, or local checkpoint | checklist | Exact, authorized Git transition |
| A large authorized task is still in progress and needs durable milestones | execution durability | Bounded milestone/fixup/checkpoint state |
| Conflicts or divergent-history strategy is actually needed | resolving merge conflicts | Resolved/blocked integration path |
| Fixup/checkpoint normalization is authorized | history normalization | Tree-proven normalized history |
| Catalog release applies | skills release | Fixed-basis catalog delivery |
| Need final report | delivery report | Evidence-bounded outcome |
Invariants
- No commit/push/integration/cleanup follows from implementation or review wording alone.
- Stage only frozen exact paths; never use broad pathspecs or hide unrelated dirty content.
- Ordinary commit/push does not require a merge strategy; apply it only for actual divergent integration.
- Report local and remote refs separately; never claim publication, merge, or runtime installation without evidence.
Output Map
Report authorized mode, basis, exact staged scope, validation/review state, local SHA, remote result if applicable, residual Worktree, and every unverified boundary.
Reference Map
- Read checklist for every mutation. Read execution durability only for the in-progress large-task route; ordinary completed-change commit/push does not load it.
- Read resolving merge conflicts, history normalization, skills release, and delivery report only when their route applies.
- Read usage for modes/boundaries.
- Maintainers only: read eval cases; do not load it during ordinary runtime.