github / spec-kit
💫 Toolkit to help you get started with Spec-Driven Development
github.com/github/spec-kitIndexed at 1b0556cUp to date with upstream
About this codebase
337 files and 3,352 symbols in 5 modules, led by Python (170 files) and Shell (11).
Built from the index
Code health
This codebase scores 5.1 out of 10 for code health, which we rate needs work. Risk is concentrated, as it usually is: 39 of 337 files are git hotspots, and they average 4.0 — which is where the fixes pay off most.
On the leaderboards:#42 of 44 Python repos
Do next
Nothing stands out in the week to Jun 11, the last indexed commit.
Improve what Repowise can see
Add a test coverage report
Without one, Repowise cannot tell tested code from untested code, so every test-related action says “unknown”.
- line coverage
- Unknown, no report
Small effort
Use github/spec-kit in your agent
Point Claude Code, Cursor, Codex or VS Code at this repository. Your agent gets the index this page is built from: cited answers, callers, history and health for any file.
https://api.repowise.dev/mcp/github/spec-kitOne command, run anywhere. Adds the server to your local Claude Code config.
Docsclaude mcp add --transport http repowise https://api.repowise.dev/mcp/github/spec-kit \ --header "Authorization: Bearer rw_live_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
This repo is public, so anyone with a Repowise account and an API key can connect.
Try asking
- get_overview()
- get_answer("how is spec-kit put together?")
- get_why("why is spec-kit structured this way?")
Prefer local? pip install repowise && repowise init indexes your own checkout, no account needed.
Go deeper
- OverviewEverything the index found, what changed this week, commits and decisions.
- DocumentationModule-by-module documentation, written from the source.
- ArchitectureDependency graph, layers and third-party dependencies.
- Code healthEvery file's score, the findings behind it, tests and refactoring plans.
- CommitsEach commit's effect on code health, with agent provenance.
- ContributorsWho owns what, and where one person holds most of the knowledge.
- DecisionsArchitectural decisions mined from commits and pull requests.
- Ask this codebaseSign inGrounded answers over the indexed code.
Maintain this repo? Claim the page
Sign in with GitHub and we check that you are an admin or maintainer of github/spec-kit. Then add a badge to the README that links readers here.
Use this repo from Claude or ChatGPT
Add this URL as a custom connector and sign in with repowise when asked. No API key to copy.
https://api.repowise.dev/mcp/github/spec-kitFor maintainers
Add a badge to your README
Every badge is public, cached, and updates on its own after every index. Nothing to install.
Repowise badge
Links to this page, with no score on it. Adding it also re-indexes the repo every week.
[](https://repowise.dev/repo/github/spec-kit?src=badge_wiki)Code health badge
The repo's health score out of 10, from the latest index.
[](https://repowise.dev/repo/github/spec-kit?src=badge_health)Code health card
A larger card with the score, its change since the last index, and when it was measured. The HTML version follows the reader's light or dark theme.
[](https://repowise.dev/repo/github/spec-kit?src=badge_card)How github/spec-kit works
💫 Toolkit to help you get started with Spec-Driven Development This page is a map of the github/spec-kit repository, written primarily in Python, rebuilt from the source each time it is indexed. Repowise parses every symbol, computes a dependency graph, scores per-file code health from complexity, duplication, test coverage and churn, mines git history for hotspots and ownership, and lifts the architectural decisions into documentation you can read here or query through MCP.
The codebase has 337 files and 3,352 symbols in 5 modules, led by Python and Shell. Code health is 5.1 out of 10, rated needs work.
Use the links above to open each view, or connect this repository to your agent for grounded answers inside Claude, Cursor, Codex or VS Code.