Opinionated backlog-standards toolkit: spec-driven cross-repo lint and conformance reports for GitHub issues (MCP server + CLI).
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"issue-kit-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# issue-kit Opinionated backlog-standards toolkit: a single spec file (`issue-standard.yml`) declares your issue standard — label taxonomy with colors, the required `.github/ISSUE_TEMPLATE` set, lint rules — and issue-kit checks any number of repositories against it. MCP server and CLI over one engine. Phase M0 is strictly **read-only**: it lints and reports, it never mutates a repository. The only write is `standard_init`, which puts the default spec on your local disk. Design docs live in [ARCHITECTURE.md](ARCHITECTURE.md), [ROADMAP.md](ROADMAP.md), and [adr/](adr/). ## Install ```bash pip install issue-kit-mcp # or from a checkout: pip install -e '.[dev]' ``` Requires Python 3.10+. ## CLI ```bash # Write the default spec (standard 2026-07-14) to ./issue-standard.yml issue-kit init [--path PATH] [--force] # Lint one or more repos against the spec issue-kit lint OWNER/REPO [OWNER/REPO ...] [--repo OWNER/REPO] [--repos-file FILE] [--spec PATH] [--provider github|snapshot] [--snapshots DIR] [--format json|text|markdown] [--ci] # Aggregate conformance dashboard issue-kit report OWNER/REPO ... [--repos-file FILE] [--spec PATH] [--provider github|snapshot] [--snapshots DIR] [--format json|text|markdown] # Capture a repo's issues/labels/templates into a snapshot bundle (GET-only) issue-kit snapshot OWNER/REPO --out DIR [--format json|text|markdown] ``` `standard-init` / `standard-lint` / `standard-report` / `standard-snapshot` are accepted aliases — the same naming the MCP tools use (`snapshot` is CLI-only in M0; it has no MCP double yet). ### Exit codes Shared CI contract (never masked): | code | meaning | |---|---| | 0 | conformant, or advisory-only findings | | 1 | error-severity findings present | | 2 | config error: invalid spec, provider/auth failure, invalid arguments | stdout carries the report in the chosen format (parseable even at exit 1); stderr carries diagnostics. Default forma…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.