auto
Run a SpecWeave increment unattended until every task is done, then verify and close - the Unattended section of sw-do. Use for…
@anton-abyzovInstall SkillDevelopment
Skill
/sw-sync
Sync SpecWeave increments with GitHub, Jira or Azure DevOps - push progress, pull or import issues, check token and health, run setup. Use for "sync", "push to GitHub", "import issues".
Claude Code
$ npx -y skills add anton-abyzov/specweave --skill sw-sync --agent claude-code
Codex
$ npx skills add anton-abyzov/specweave --skill sw-sync -a codex -y
Cursor
$ npx skills add anton-abyzov/specweave --skill sw-sync -a cursor -y
Gemini CLI
$ npx skills add anton-abyzov/specweave --skill sw-sync -a gemini-cli -y
GitHub Copilot
$ npx skills add anton-abyzov/specweave --skill sw-sync -a github-copilot -y
OpenCode
$ npx skills add anton-abyzov/specweave --skill sw-sync -a opencode -y
Windsurf
$ npx skills add anton-abyzov/specweave --skill sw-sync -a windsurf -y
SKILL.md
sw-sync.SKILL.mddescription: Sync SpecWeave increments with GitHub, Jira or Azure DevOps - push progress, pull or import issues, check token and health, run setup. Use for "sync", "push to GitHub", "import issues".
argument-hint: "push|pull|status|setup [increment-id]"
metadata:
version: "3.0.0"
sw-sync: external tracker sync
Sync is opt-in and explicit. Starting, pausing or completing an increment never calls a tracker; only `specweave sync push` does (plus close-on-complete, when configured). Go through the CLI, never `gh`, `curl` or a provider API directly: the CLI owns token resolution, the rate budget, duplicate detection and the links in both directions.
Commands
| Intent | Command | |---|---| | Push progress to issues | `specweave sync push [increment-id]` | | Preview a push | `specweave sync push 0042 --dry-run` | | One provider only | `specweave sync push 0042 --provider github` | | Report external changes | `specweave sync pull [--since 7]` | | Import issues as increments | `specweave sync pull --create-increments` | | Token, account, health, retry queue | `specweave sync status [--json]` | | Connect a provider | `specweave sync setup [--provider github]` | | Check an existing setup | `specweave sync setup --validate` |
`sync status` exits 1 when anything needs attention.
Providers
Read the provider from `.specweave/config.json`; never guess. GitHub is first-class. Jira and Azure DevOps are supported and opt-in: push and close are covered, say so before promising more.
Tokens resolve in one order: config, then `GITHUB_TOKEN` / `GH_TOKEN`, then the project `.env`, then `gh auth token`. `sync status` prints which one won and for which account. A 404 on write means that account cannot write to the repository: fix the token, do not retry. Check a token exists without printing it.
Rules
1. `--dry-run` first when an increment has never synced. 2. Never edit the issue links in `metadata.json` by hand; a broken link is fixed with `specweave sync push 0042 --force`. 3. Report `sync status` output as it is when it shows problems; do not paraphrase token or permission errors.
Manual path (no CLI)
There is no manual sync. Update the issue yourself and put its URL in spec.md Problem so the next agent can find it.
Read more
description: Sync SpecWeave increments with GitHub, Jira or Azure DevOps - push progress, pull or import issues, check token and health, run setup. Use for "sync", "push to GitHub", "import issues". argument-hint: "push|pull|status|setup [increment-id]" metadata: version: "3.0.0"
sw-sync: external tracker sync
Sync is opt-in and explicit. Starting, pausing or completing an increment never calls a tracker; only `specweave sync push` does (plus close-on-complete, when configured). Go through the CLI, never `gh`, `curl` or a provider API directly: the CLI owns token resolution, the rate budget, duplicate detection and the links in both directions.
Commands
| Intent | Command | |---|---| | Push progress to issues | `specweave sync push [increment-id]` | | Preview a push | `specweave sync push 0042 --dry-run` | | One provider only | `specweave sync push 0042 --provider github` | | Report external changes | `specweave sync pull [--since 7]` | | Import issues as increments | `specweave sync pull --create-increments` | | Token, account, health, retry queue | `specweave sync status [--json]` | | Connect a provider | `specweave sync setup [--provider github]` | | Check an existing setup | `specweave sync setup --validate` |
`sync status` exits 1 when anything needs attention.
Providers
Read the provider from `.specweave/config.json`; never guess. GitHub is first-class. Jira and Azure DevOps are supported and opt-in: push and close are covered, say so before promising more.
Tokens resolve in one order: config, then `GITHUB_TOKEN` / `GH_TOKEN`, then the project `.env`, then `gh auth token`. `sync status` prints which one won and for which account. A 404 on write means that account cannot write to the repository: fix the token, do not retry. Check a token exists without printing it.
Rules
1. `--dry-run` first when an increment has never synced. 2. Never edit the issue links in `metadata.json` by hand; a broken link is fixed with `specweave sync push 0042 --force`. 3. Report `sync status` output as it is when it shows problems; do not paraphrase token or permission errors.
Manual path (no CLI)
There is no manual sync. Update the issue yourself and put its URL in spec.md Problem so the next agent can find it.
Stats
170
Stars
20
Forks
Active
Maintenance
TypeScript
Language
MIT
License
Last commit
Created
Ships withspecweave
Open-source spec CLI: the spec, tasks and proof of done live in git, so any AI coding agent (Claude Code, Codex, Cursor, Copilot) can pick up where another stopped. Powers SpecWithCode: specwithcode.com
17018 skills1 agent
Stars on GitHub
Momentum
- stars in total
- 170
Other skills on specweave.
@anton-abyzovInstall Skilldo
Work a SpecWeave increment task by task - claim, implement inside its Files, test, commit, done with evidence - alone, unattended…
@anton-abyzovInstall Skilldone
Close a SpecWeave increment - every task done or skipped, specweave verify green, a fresh-context review, then specweave…
@anton-abyzovInstall Skillgrill-me
Interview the user relentlessly, in rounds, until every decision in a plan is settled; facts are your job, decisions are theirs.…
@anton-abyzovInstall Skillhandoff
Hand work to another tool, account or machine and pick it up there, in two words. Use when the user says "hand off", "hand off…
@anton-abyzovInstall Skillincrement
Plan work as a SpecWeave increment - one spec.md with Problem, Scope, numbered ACs, Approach and Tasks - before writing code. Use…
@anton-abyzovInstall SkillMore skills from other plugins.
Auto-invoked
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
@obraInstall Skillask-matt
Ask which skill or flow fits your situation. A router over the skills in this repo.
@mattpocockInstall SkillAuto-invoked
Questions about sw-sync.
- Which coding agents can use sw-sync?
- sw-sync installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.