Skill
auto
Run a SpecWeave increment unattended until every task is done, then verify and close. Use for "auto mode", "run until done", "ship this while I sleep".
@anton-abyzovView 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".
Install
$ npx -y skills add anton-abyzov/specweave --skill sw-sync --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/sw-sync
Context preview
The summary Claude sees to decide when to auto-load this skill.
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".
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]"
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]" 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.
Ships withspecweave
Spec-first AI development: describe a feature → AI creates spec + plan + tasks, builds autonomously, syncs to GitHub/JIRA. Domain-expert skills for PM, Architect, Frontend, QA learn your patterns permanently. Claude Code, Codex, Cursor, Copilot & more.
Get the whole plugin
Stats
164
Stars
21
Forks
Active
Maintenance
TypeScript
Language
MIT
License
11h ago
Last commit
11mo ago
Created
Repo: anton-abyzov/specweave
In this plugin
See everything inside Other skills on specweave.
@anton-abyzovView SkillSkill
brainstorm
Widen the options before committing - framed options compared on stated criteria, ending in a pick that becomes an increment. Use for "brainstorm", "ideate",…
@anton-abyzovView SkillSkill
do
Work a SpecWeave increment task by task - claim, implement inside the task's Files, test, commit, done with evidence - then verify and close. Use for…
@anton-abyzovView SkillSkill
done
Close a SpecWeave increment - every task done or skipped, specweave verify green, a fresh-context review, then specweave complete. Use for "close it", "we are…
@anton-abyzovView SkillSkill
handoff
Hand work to another tool, account or machine and pick it up there, in two words. Use when the user says "hand off", "out of tokens", "switching accounts",…
@anton-abyzovView SkillSkill
increment
Plan work as a SpecWeave increment - one spec.md with Problem, Scope, numbered ACs, Approach and Tasks - before writing code. Use for "plan a feature", "new…
@anton-abyzovView Skill