spec-probe

Check code against functional requirements in a spec (.md / .docx / .pdf). Use VS Code Copilot chat (/spec-cover, …) or the spec-probe CLI.

Install

pip install spec-probe
spec-probe-skill --vscode

Python ≥ 3.11. Reload VS Code after spec-probe-skill.

Optional: sudo apt install ripgrep (faster search on Linux).

Configure

Edit ~/.config/spec-probe/:

• .env — EXACODE_API_KEY (and other keys if you change LLM jobs in config.json).
• config.yaml — absolute paths:

input:
  module_path: /abs/path/to/your/app
  spec_path: /abs/path/to/spec.md
  related_modules:
    paths:
      - /abs/path/to/other/service

Codegraph (optional)

Needs Node.js.

spec-probe-codegraph /abs/path/to/module

With related_modules, index the monorepo root. After big changes: codegraph sync /abs/path/to/monorepo-root.

Chat workflow (VS Code Copilot)

Large spec: parse → a few FRs or one section → verify. Verify/check → chat only; ask for a report when you need files.

CLI (optional)

spec-probe verify --module /abs/app --spec /abs/spec.md --fr FR-001
spec-probe check "The module shall …"
spec-probe parse --spec /abs/spec.md --summary

Paths default from ~/.config/spec-probe/config.yaml when omitted.

License

MIT — see LICENSE. Maintainers: docs/PYPI.md.