workbench-sync
Sync workflows for Workbench CLI. Use when aligning local work items with GitHub issues, creating branches, or reconciling doc backlinks.
Installation
Follow the repository instructions for this skill and your agent. Review the files and dependencies before adding it to your workflow.
View source ↗GuidesSkill instructions
Key settings
-
.workbench/config.json: github.owner, github.repository, github.host, git.defaultBaseBranch. - Ensure
gh auth loginis complete before syncing issues.
Core workflows
- Import missing GitHub issues into local work items.
- Create missing GitHub issues for active work items.
- Create branches for active items.
- Sync doc backlinks and front matter.
Commands
Dry-run sync:
workbench.ps1 sync --dry-run
Sync a specific item and prefer GitHub content:
workbench.ps1 item sync --id TASK-0001 --prefer github
Bulk sync (local wins on conflicts):
workbench.ps1 sync --items
Import unlinked GitHub issues (slower):
workbench.ps1 sync --items --import-issues
Sync doc backlinks (include done items when needed):
workbench.ps1 doc sync --all
workbench.ps1 doc sync --all --include-done
Output
- New work items from GitHub issues.
- New GitHub issues and branches for active work items.
- Updated doc backlinks and front matter.
Guardrails
- Use
--dry-runbefore creating issues or branches. -
workbench.ps1 syncdefaults to linked work items only; use--import-issuesto pull unlinked GitHub issues. - Terminal items (done/dropped) do not create issues or branches by default.
- Sync is not a replacement for specs/ADRs; create or update them during planning.
Examples
Read the usage examples in the source repository.
View source ↗Source history
- Indexed on
- 2026-01-20
- Index updated
- 2026-01-26
- Branch
- main
Index and sync dates describe this directory. View the source repository for code history.
GitHub ↗chat Comments (0)
Sign in to join the discussion and leave a comment.
No comments yet. Be the first to share your thoughts!