publish

Review and execute approved Git pushes with bound destinations, verification, and CI rerun handling.

1|Updated Mar 6, 2026
One-click install
npx skills add https://github.com/peregrinus879/eyragents --skill publish-peregrinus879
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: publish
Source: https://github.com/peregrinus879/eyragents/tree/main/agents/.agents/skills/publish
Command: npx skills add https://github.com/peregrinus879/eyragents --skill publish-peregrinus879

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Publishing commits via push, release, or pull request can expose unreviewed content, credentials, or wrong destinations. This Skill enforces a review-then-execute workflow so every publication is bound to an exact reviewed commit and destination before it goes out. ## Core Features & Use Cases - Binding and review: The publish-bind script scans newly reachable commits, objects, and diffs, then binds one resolved push endpoint, branch, and reviewed commit to an immutable ID. - Controlled execution: publish-apply performs a single force-with-lease push per approved binding with normal hooks enabled, and publish-verify confirms the remote state via read-only ls-remote and repository verification targets. - CI rerun handling: Diagnoses failed CI jobs on the exact published commits and performs bounded gh run rerun retries without requiring a second approval. - Use Case: Before pushing a release branch to a shared remote, run the publish workflow to review every new commit, get one consolidated approval for the push set, execute each binding in order, and verify the remote state and CI results. ## Quick Start Ask the agent to run the publish skill to review and push the current HEAD to its tracked remote with full verification.

Frequently Asked Questions about publish

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I safely review commits before pushing to a remote?

Run the publish-bind script on the target ref to scan every newly reachable commit, object, and diff for sensitive content, then bind the reviewed tip to an immutable ID. Only after human approval does publish-apply execute the exact bound push.

How does the publish skill prevent pushing to the wrong destination?

Each binding records one resolved endpoint, branch, reviewed commit, and tracking baseline, refusing multiple destinations, embedded credentials, and missing baselines. Execution uses force-with-lease against the reviewed remote base so drift stops the push.

Can I retry a failed CI job after publishing commits?

Yes, the original publication approval covers bounded retries of failed CI for the exact published commits. The workflow inspects the run with gh run view, diagnoses a retryable cause, and uses gh run rerun scoped to the failed job.

What happens if a push fails or times out during execution?

The attempt consumes that binding's execution opportunity and is recorded as attempted; it is never replayed or reset to ready. Verification still runs where possible, and continuing the remaining set requires a fresh summary and approval.

Does the publish workflow work in Codex or restricted environments?

Codex retains command-network and protected-file restrictions, so publish-apply cannot run there natively. The workflow hands off to a Claude Code, OpenCode, or Hermes session in the same repository, which re-reviews and obtains fresh approval.