workbench-sync

Files (1)

• SKILL.md

SKILL.md (first lines)

## Key settings

- [`.workbench/config.json`](../../.workbench/config.json): github.owner, github.repository, github.host, git.defaultBaseBranch.
- Ensure `gh auth login` is complete before syncing issues.

## Core workflows

1. Import missing GitHub issues into local work items.
2. Create missing GitHub issues for active work items.
3. Create branches for active items.
4. Sync doc backlinks and front matter.

## Commands

Dry-run sync:
```bash
workbench sync --dry-run
```

Sync a specific item and prefer GitHub content:
```bash
workbench item sync --id WI-WB-0001 --prefer github
```

Bulk sync (local wins on conflicts):
```bash
workbench sync --items
```

Import unlinked GitHub issues (slower):
```bash
workbench sync --items --import-issues
```

Sync doc backlinks (include terminal items when needed):
```bash
workbench doc sync --all
workbench doc sync --all --include-terminal-items
```

## 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-run` before creating issues or branches.
- `workbench sync` defaults to linked work items only; use `--import-issues` to pull unlinked GitHub issues.
- Terminal items (complete/cancelled/superseded) do not create issues or
  branches by default.
- Sync is not a replacement for specifications or architecture artifacts;
  create or update them during planning.

From incursa/workbench, Apache-2.0.

More from incursa/workbench