review
01Command Claude Code
A three-pass editing command for improving an article's content, style, and level of detail.
92 tagged spec-kit, measured the same way as everything else here.
Browse within: spec-driven-development 62github-copilot 48prompt-engineering 30templates 30vibe-engineering 30spec-driven 20copilot-coding-agent 18ai-article-writer 16article 16ai-context 14markdown 14speckit 14spec-kit-extension 7research-harness 6
Command Claude Code
A three-pass editing command for improving an article's content, style, and level of detail.
Command GitHub Copilot
Command description: Run implement and QC in a continuous loop. Argument hint: [optional: feature directory or branch name] Command category: orchestration Prerequisites: spec, plan, tasks.
lindoelio/spec-driven-steroids
Command Claude Code
Generate or refresh repository guideline documents using the project-guidelines-writer skill. Analyze the repo, generate all six standard guideline files by default, prefer managed-section updates for existing files, and ask only for exceptional overwrite or skip decisions.
Command Claude Code needs its repo
Archive a feature specification into main project memory after merge, resolving gaps and conflicts.
Command Claude Code
Capture durable knowledge and architecture decisions from current or provided diffs.
tinesoft/spec-kit-token-budget
Command Claude Code
Compact one or more Spec-Driven Development artifacts in place to reduce token cost on subsequent /speckit. commands. Lossless on requirements, decisions, contracts, IDs; strips template scaffolding, examples, and prose padding. The original is preserved as .full.md the first time an artifact is compacted.
Command Claude Code
Run a budget-aware exploration loop that externalizes every finding into the harness state files.
Command Codex
This prompt is specific to the codexshell project.
Command GitHub Copilot needs its repo
Generate pull request review using architecture overview context.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: