Agent skill
workbench-sync
Sync workflows for Workbench CLI. Use when aligning local work items with GitHub issues, creating branches, or reconciling doc backlinks.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/data/workbench-sync
SKILL.md
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.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?