Publishing
Opt in, and honey-stack turns what it learns into GitHub issues and evaluated skill PRs — and, if you allow it, merges and releases them for every install.
Updated
Turn it on
Run this from your honey-stack source checkout. It pins the repository and default branch in your local config.
honey rsi publish on # issues + PRs, review-only merges
honey rsi publish automatic # also CI-gated merges, releases and auto-updates
honey rsi publish status --json
honey rsi publish offPublishing needs authenticated gh with permission to create issues, push branches and open PRs.
The full flow
- Suggestion → GitHub issue. Pending toolkit diagnoses, new-skill ideas and upstream proposals become issues during normal RSI processing — even with automatic application off. Each issue says it's unimplemented and needs confirmation.
- Evaluation. The candidate runs against generated, matched and behaviour cases.
- Apply and sync locally. The patch applies to your install and syncs to both agents.
- Skill-only commit → PR. Commits start from the remote base and contain only the evaluated
skills/<name>/SKILL.md. - CI-gated merge (automatic mode). Only after all four CI test jobs pass, the exact head and evaluated base still match, and review requirements are met.
- Release and install. The main workflow publishes a versioned release; later RSI passes detect it and install it.
What's shared, what stays local
Issues share only a bounded, redacted title, diagnosis and proposed next step. Session quotes, session ids and local evidence are excluded. PR text uses fixed metadata — never your quotes or the model's rationale. The skill text itself is shared.
Personal preferences, instruction files, machine repairs, guards, session logs and generated evaluation prompts stay local. Local evaluation commits and their history are never pushed.
Guarantees
No admin bypass and no force push, ever. Missing checks, failures, changed revisions, requested changes and conflicts remain visible blockers. Closed issues aren't recreated and a closed PR is respected. Failed GitHub requests retry later and look for an existing issue or PR first. A publication failure never undoes a successful local application.
A clean local checkout still at the private evaluation commit is preserved in an rsi/applied-backup-* branch before moving to the public release. New local commits, uncommitted work or a different branch prevent reconciliation.