/github-sync
[DEPRECATED] GitHub sync guidance. Superseded by the live sw-github:* command family. For actual syncing use sw-github:push / sw-github:pull / sw-github:close / sw-github:sync.
$ npx -y skills add anton-abyzov/specweave --skill github-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
/github-sync
Context preview
The summary Claude sees to decide when to auto-load this skill.
[DEPRECATED] GitHub sync guidance. Superseded by the live sw-github:* command family. For actual syncing use sw-github:push / sw-github:pull / sw-github:close / sw-github:sync.
SKILL.md
github-sync.SKILL.mddescription: "[DEPRECATED] GitHub sync guidance. Superseded by the live sw-github:* command family. For actual syncing use sw-github:push / sw-github:pull / sw-github:close / sw-github:sync."
version: 1.0.1
user-invokable: false
deprecated: true
> ⚠️ DEPRECATED — superseded by the live `sw-github:*` command family.
This skill's standalone guidance is retired. GitHub sync is performed by the increment-based command family, which is the source of truth:
| Action | Live command | |--------|--------------| | Push local progress to GitHub Issues | `sw-github:push [increment-id]` | | Pull issue state back into the spec | `sw-github:pull` | | Create the GitHub Issue/milestone | `sw-github:create` | | Close issues on increment completion | `sw-github:close` | | Two-way reconcile | `sw-github:sync` | | Check sync status | `sw-github:status` |
**Mapping** (per CLAUDE.md): Feature → Milestone · User Story → Issue · Task → Checkbox.
Why this skill is deprecated
- The increment-based `sw-github:*` commands are the supported path. Run them
directly; this skill no longer carries its own workflow guidance (it was contradictory — it pointed at a `sw-github:sync-spec` command that does not exist and claimed increment-based sync was "removed" when it is the live flow).
- Setup and credentials are handled by `sw:sync-setup`. Configuration lives in
`.specweave/config.json` (`sync.*`); the GitHub token is read from `GITHUB_TOKEN` / `GH_TOKEN` in `.env` (or `gh auth login`).
- For the deprecation policy, see
`.specweave/docs/internal/specs/skill-deprecation-policy.md`.
Removal
Scheduled for removal once the `sw-github:*` command help fully absorbs any remaining setup notes. Until then this stub exists only to avoid contradictory guidance; it is non-activating (`user-invokable: false`).
Read more
description: "[DEPRECATED] GitHub sync guidance. Superseded by the live sw-github:* command family. For actual syncing use sw-github:push / sw-github:pull / sw-github:close / sw-github:sync." version: 1.0.1 user-invokable: false deprecated: true
> ⚠️ DEPRECATED — superseded by the live `sw-github:*` command family.
This skill's standalone guidance is retired. GitHub sync is performed by the increment-based command family, which is the source of truth:
| Action | Live command | |--------|--------------| | Push local progress to GitHub Issues | `sw-github:push [increment-id]` | | Pull issue state back into the spec | `sw-github:pull` | | Create the GitHub Issue/milestone | `sw-github:create` | | Close issues on increment completion | `sw-github:close` | | Two-way reconcile | `sw-github:sync` | | Check sync status | `sw-github:status` |
**Mapping** (per CLAUDE.md): Feature → Milestone · User Story → Issue · Task → Checkbox.
Why this skill is deprecated
- The increment-based `sw-github:*` commands are the supported path. Run them
directly; this skill no longer carries its own workflow guidance (it was contradictory — it pointed at a `sw-github:sync-spec` command that does not exist and claimed increment-based sync was "removed" when it is the live flow).
- Setup and credentials are handled by `sw:sync-setup`. Configuration lives in
`.specweave/config.json` (`sync.*`); the GitHub token is read from `GITHUB_TOKEN` / `GH_TOKEN` in `.env` (or `gh auth login`).
- For the deprecation policy, see
`.specweave/docs/internal/specs/skill-deprecation-policy.md`.
Removal
Scheduled for removal once the `sw-github:*` command help fully absorbs any remaining setup notes. Until then this stub exists only to avoid contradictory guidance; it is non-activating (`user-invokable: false`).
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.
Repo: anton-abyzov/specweave
Other skills on specweave.
- /ado-mapper
Bidirectional conversion between SpecWeave increments and Azure DevOps work items. Use when exporting increments to ADO epics, importing ADO epics as increments, or resolving sync conflicts. Handles Epic/Feature/User Story/Task hierarchy mapping.
Open skill - /ado-multi-project
[DEPRECATED] Use `sw:multi-project --tool ado` instead. Organizes specs and tasks across multiple Azure DevOps projects. This skill will be removed in SpecWeave v1.3.0.
Open skill - /ado-resource-validator
Validates Azure DevOps projects, area paths, and teams exist with auto-creation of missing resources. Use when setting up ADO integration, configuring .env variables, or troubleshooting missing project errors. Supports project-per-team, area-path-based, and team-based strategies.
Open skill - /ado-sync
[DEPRECATED] Help and guidance for Azure DevOps synchronization with SpecWeave increments. Use when asking how to set up ADO sync, configure credentials, or troubleshoot integration issues. For actual syncing, use sw-ado:push or sw-ado:pull command.
Open skill - /analytics
Analytics and metrics for SpecWeave usage — token consumption, cache efficiency, agent spawn counts.
Open skill - /architect
System architect for scalable technical designs and ADRs. Use for system architecture, microservices, database design, trade-off analysis, component diagrams, tech selection.
Open skill

