Autonomous development for real products. Governed agents build from specs you approve, follow the rules you set, and nothing merges until another agent proves it. Your decisions, judgement and taste are the bar that work must clear. Declare your vision and let agents build it.
JavaScript agentic-codingai-agentsai-governanceautonomous-agentsclaude-codeclicode-reviewcodexcoding-agentsdeveloper-toolsgit-hooksllmlocal-firstmulti-agentsoftware-factoryspec-driven-developmentverificationvibe-coding
docs(skills): share a board through the git remote with pullboard sync [I11]
Corey Olsonfca4f3ff647a
diff --git a/skills/pullboard-run/SKILL.md b/skills/pullboard-run/SKILL.mdindex 6994451d..c5f14bcc 100644--- a/skills/pullboard-run/SKILL.md+++ b/skills/pullboard-run/SKILL.md@@ -162,6 +162,7 @@ At the start of every coordinator cycle, check the flow from the `flow:` line in- When validating a project before planning, run `pullboard doctor`; when a published Claude Code skill changed, run `pullboard skills --update` to refresh only unchanged installed copies.- When hooks are missing after a clone, run `pullboard hooks` to reinstall them; when diagnosing one hook directly, run `pullboard hook pre-commit`, `pullboard hook pre-merge-commit`, `pullboard hook commit-msg`, or `pullboard hook pre-push` for the hook in question.- When linking this board to the relay, run `pullboard relay on`; use `pullboard relay off` to unlink it, `pullboard relay pair` to print a one-use code, and `pullboard relay join <code>` in the clone that receives that code. Run `pullboard relay` to inspect link state.+- When two machines should share one board without a pullboard.dev account, run `pullboard sync` to opt in to sharing it through the repo's git remote; reads work offline, and moves wait for the remote to acknowledge them.- When checking paired-device or agent-token metadata, run `pullboard relay devices` or `pullboard relay tokens`; use `pullboard relay revoke <id>` only when authorized to revoke that device or token. When a blocked relay position needs recovery, hand it to the person because recovery is reserved for their action.- For an additional phone or browser, the person runs `pullboard relay pair --new-browser` on the linked computer and opens its fresh one-use link in that browser. Bare `pullboard relay pair` still creates the computer-clone code; `pullboard relay on --all` keeps its first-phone-only behavior.- When opening the local board in a browser, run `pullboard view`; use `pullboard view --export <dir>` for a static snapshot and `pullboard serve` when a local script needs the authenticated API.