Run any Skill in Manus with one click

dev-spec-kit-revitify

Stars0

Forks0

UpdatedJune 20, 2026 at 07:17

dev-spec-kit's default code-graph provider — the bundled revitify engine (native TypeScript, tree-sitter multi-language). Zero install, zero API key, always available. Use to understand when revitify is the right provider, how it is configured, what it can and cannot index, and how it feeds the Verified Traceability Graph. For the build/read loop itself, see dev-spec-kit-graph.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

Pratiyush

Pratiyush/dev-spec-kit

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	dev-spec-kit-revitify
description	dev-spec-kit's default code-graph provider — the bundled revitify engine (native TypeScript, tree-sitter multi-language). Zero install, zero API key, always available. Use to understand when revitify is the right provider, how it is configured, what it can and cannot index, and how it feeds the Verified Traceability Graph. For the build/read loop itself, see dev-spec-kit-graph.

revitify — the bundled, default graph provider

revitify is dev-spec-kit's built-in code-graph engine: a native-TypeScript indexer (tree-sitter, multi-language, with a cache and workers). It ships inside dev-spec-kit as a normal dependency, so it is always available — no pip, no external binary, no API key. It is the default value of graphify.provider and the right choice for essentially every project.

What it does

Walks the repo and indexes source across languages into nodes (functions / classes / files) and their import/call links, writing the graphify-out/graph.json contract that dev-spec-kit ingests as codeNodes and overlays proven edges onto.
Runs on dev-spec-kit graph build with nothing to configure — it is already the default.
Reports as always-OK under dev-spec-kit doctor (it cannot be "missing" — it is bundled).

When revitify is the right provider

Code-only projects — i.e. almost all of them. If the spec's evidence lives in source code, revitify is strictly better than the alternative: same graph contract, zero install cost.
Choose the other provider only when you must index non-code artifacts (PDFs, images, video) — that is the sole reason to leave the default. See dev-spec-kit-graphify.

Provenance

revitify is an independent MIT port of the Python "graphify" project (github.com/safishamsi/graphify). graphify is credited as the upstream inspiration and is never a runtime dependency of revitify — the bundled engine stands alone.

Rules

revitify is bundled and ALWAYS available — you MUST NOT switch to the external graphify provider merely to avoid an install. That trades a working default for an external dependency and buys nothing on a code-only project.
graphify-out/ is derived — NEVER hand-edit or commit it; regenerate via dev-spec-kit graph build.
For the build/refresh wrapper, reading blast radius / implements-edges, and the staleness re-prove dance, follow dev-spec-kit-graph — those mechanics are provider-agnostic and identical here.

More from this repository

same repository

dev-spec-kit-graph

Pratiyush/dev-spec-kit

Build, refresh, and read dev-spec-kit's Verified Traceability Graph — provider-agnostic. Keep it fresh with the build wrapper, read blast radius / implements-edges / drift to answer "what breaks if this changes?", and run the staleness re-prove dance. For choosing and configuring the code-graph engine itself, see the dev-spec-kit-revitify and dev-spec-kit-graphify skills.

2026-06-200

dev-spec-kit-graphify

Pratiyush/dev-spec-kit

dev-spec-kit's optional code-graph provider — the external Python graphify tool (multi-modal: indexes PDFs, images, and video alongside code). Opt-in only. Use to decide when graphify is worth its install over the bundled revitify default, how to install and configure it, and how dev-spec-kit verifies and falls back when it is absent. For the build/read loop itself, see dev-spec-kit-graph.

2026-06-200

dev-spec-kit-workflow

Pratiyush/dev-spec-kit

Drive spec-driven development with dev-spec-kit — route the request, write EARS specs with @check bindings, derive evidence-bound tasks, TDD, prove checks with real test runs, build the Verified Traceability Graph, record approvals, and generate graph-derived PR bodies. Use whenever the user asks to build/change code in a dev-spec-kit-initialized project (.dev-spec-kit/ present) or mentions rivet, specs, EARS, or traceability.

2026-06-200

dev-spec-kit-analyze

Pratiyush/dev-spec-kit

Score each requirement's complexity 1–10 and recommend a subtask breakdown, then expand the over-scoped ones into bound sub-criteria. Use after a spec is drafted and before implementation, to catch requirements that are too big to prove as a single unit.

2026-06-190

dev-spec-kit-architect

Pratiyush/dev-spec-kit

Turn approved requirements into a thin high-level design and the Architecture Decision Records (ADRs) that justify the non-obvious choices. Use after requirements are clarified and before implementation, or when a change makes a load-bearing architectural decision.

2026-06-190

dev-spec-kit-clarify

Pratiyush/dev-spec-kit

Resolve ambiguity in a raw intake or draft spec by asking the user ≤5 high-value questions, each with a recommended default. Use before finalizing a full-spec route, or when `spec.onVague` is "clarify", or whenever a requirement is under-specified.

2026-06-190

name	dev-spec-kit-revitify
description	dev-spec-kit's default code-graph provider — the bundled revitify engine (native TypeScript, tree-sitter multi-language). Zero install, zero API key, always available. Use to understand when revitify is the right provider, how it is configured, what it can and cannot index, and how it feeds the Verified Traceability Graph. For the build/read loop itself, see dev-spec-kit-graph.

revitify — the bundled, default graph provider

What it does

Walks the repo and indexes source across languages into nodes (functions / classes / files) and their import/call links, writing the graphify-out/graph.json contract that dev-spec-kit ingests as codeNodes and overlays proven edges onto.
Runs on dev-spec-kit graph build with nothing to configure — it is already the default.
Reports as always-OK under dev-spec-kit doctor (it cannot be "missing" — it is bundled).

When revitify is the right provider

Code-only projects — i.e. almost all of them. If the spec's evidence lives in source code, revitify is strictly better than the alternative: same graph contract, zero install cost.
Choose the other provider only when you must index non-code artifacts (PDFs, images, video) — that is the sole reason to leave the default. See dev-spec-kit-graphify.

Provenance

Rules

revitify is bundled and ALWAYS available — you MUST NOT switch to the external graphify provider merely to avoid an install. That trades a working default for an external dependency and buys nothing on a code-only project.
graphify-out/ is derived — NEVER hand-edit or commit it; regenerate via dev-spec-kit graph build.
For the build/refresh wrapper, reading blast radius / implements-edges, and the staleness re-prove dance, follow dev-spec-kit-graph — those mechanics are provider-agnostic and identical here.