// [DEPRECATED] GitHub issue formatting standard. See docs/internal/specs/github-issue-standard.md
| name | sw/github-issue-standard |
| description | [DEPRECATED] GitHub issue formatting standard. See docs/internal/specs/github-issue-standard.md |
| version | 1.0.0 |
| deprecated | true |
⚠️ DEPRECATED: Content moved to
.specweave/docs/internal/specs/github-issue-standard.md
Migration: This was a documentation standard, not an executable skill.
Use sw-github:push for GitHub sync operations.
Analytics and metrics for SpecWeave usage — token consumption, cache efficiency, agent spawn counts.
Batch-close all complete increments by delegating each one to `sw:done`. Discovers active/ready-for-review increments with zero pending tasks, then iterates and calls `sw:done` per increment. Use when saying "close all", "close stuck increments", or "batch close".
[DEPRECATED] Use `sw:multi-project --tool github` instead. Organizes specs and splits tasks across multiple GitHub repositories. This skill will be removed in SpecWeave v1.3.0.
Unified multi-project management skill for GitHub, Azure DevOps, and Jira. Organizes specs and splits tasks across multiple repositories or projects for monorepo, polyrepo, project-per-team, and area-path architectures. Use `--tool github|ado|jira` to select the target integration.
[DEPRECATED] Use sw:team-lead --preset <name> instead.