Prototype · Preview: every server in the official registry, synced every 30 minutes. Sign in with Google to write reviews.Prototype · updated every 30 min
PopNx MCPMCP servers for people who use AI · explained in plain words

Stet

by shamazkhanversion 0.6.5i★ 0iRuns on your computerOfficial site ↗
Registry nameio.github.shamazkhan/stet

How to install

What it does

Guardrails for AI coding agents: scope guard and locked behaviours for Claude Code, Cursor, Codex

  • Connects Runs on your computer
  • Account or key No key needed
  • Category Developer tools

Use together with

Skills that teach the AI this kind of work; they work alongside this one

rea

Reverse engineer anything with agents, from app behavior down to native binaries.

by morluto★ 467,2351 skills

Skill · How-to guide

andrej-karpathy-skills

A single CLAUDE.md file to improve Claude Code behavior, derived from Andrej Karpathy's observations on LLM coding pitfalls.

by multica-ai★ 234,1251 skills

Skill · How-to guideNo license stated

graphify

Turn any codebase, with its docs, SQL schemas, configs, and PDFs, into a queryable knowledge graph. A /graphify skill for Claude Code, Cursor, Codex, and Gemini CLI: local deterministic AST parsing, every edge explained, no vector store.

by Graphify-Labs★ 149,8731 skills

Skill · How-to guide

Why it ranks here

Lists are ordered by a usage score (out of 100) built from these parts

Popularity25/80GitHub stars or weekly downloads: the larger counts 60, the smaller 20
Freshness12/12Full marks for a release or code change within 30 days
Still answering0/8The cloud endpoint answered at the last check
Usage score37/100

Quality: Passed 3/3 basic checks (shown, not used for ordering) · Momentum: 124 (Used only on the Trending tab)

Install

Pick the AI app you use, then copy the settings.

Let your AI install it with one sentence

Please install Stet. Follow https://mcp.popnx.com/i/shamazkhan-stet.md, show me the commands and wait for my OK before running them.

Paste it into an AI that can work on your computer (such as Claude Code or Cursor). It reads our steps, shows you the commands and waits for your OK. No key, no sign-up. · See the full text your AI reads

Passed 3/3 checks · Runs on your computer · ✓ Commands checked Nov 15, 2026

First: which AI do you use?

Pick your app and the steps appear below.

Works with Claude, with some setup first

Install Node.js on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone

Let AI install it

Copy this message into a Claude chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server Stet for Claude on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "stet": { "command": "npx", "args": [ "-y", "stet-cli", "mcp" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Stet tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed

    Open the Node.js download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v

    Install once; it works for everything that needs Node.js

  2. Open the Claude desktop app’s settings file

    SettingsDeveloperEdit Config

  3. Paste these settings and save the file

    {
      "mcpServers": {
        "stet": {
          "command": "npx",
          "args": [
            "-y",
            "stet-cli",
            "mcp"
          ]
        }
      }
    }
  4. Quit Claude and open it again

  5. Try it

    Use Stet and tell me what you can do for me, then show me one thing

    ✓ If Claude says it is using Stet or shows a Stet tool in the answer, you are connected

Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version

ChatGPT cannot connect Stet yet

Stet runs on your computer, but ChatGPT can only connect servers that run on the web

What you can do instead

A · Use an app that can connect Stet

  • Install Node.js on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
  • Install Node.js on your computer first (one time)
  • Install Node.js on your computer first (one time)
  • Install Node.js on your computer first (one time)

B · Others in Developer tools that work with ChatGPT

Picked from the most used in the same category, only ones that connect by address with no key

Works with Claude Code, with some setup first

Install Node.js on your computer first (one time)

Let AI install it

Copy this message into a Claude Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server Stet for Claude Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): claude mcp add --scope user stet -- npx -y stet-cli mcp 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Stet tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed

    Open the Node.js download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v

    Install once; it works for everything that needs Node.js

  2. Open Terminal

    Mac: press Command+Space and type Terminal · Windows: open PowerShell

  3. Paste this command and press Enter

    claude mcp add --scope user stet -- npx -y stet-cli mcp
  4. Type /mcp in Claude Code

    You should see Stet listed as connected

  5. Try it

    Use Stet and tell me what you can do for me, then show me one thing

    ✓ If Claude Code says it is using Stet or shows a Stet tool in the answer, you are connected

Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with Cursor, with some setup first

Install Node.js on your computer first (one time)

Let AI install it

Copy this message into a Cursor chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server Stet for Cursor on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "stet": { "command": "npx", "args": [ "-y", "stet-cli", "mcp" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Stet tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed

    Open the Node.js download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v

    Install once; it works for everything that needs Node.js

  2. Click this button to open Cursor

    Open in Cursor

    Cursor asks you to confirm; click Install

  3. Open the AI chat in Cursor in Agent mode

  4. Try it

    Use Stet and tell me what you can do for me, then show me one thing

    ✓ If Cursor says it is using Stet or shows a Stet tool in the answer, you are connected

Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with VS Code, with some setup first

Install Node.js on your computer first (one time)

Let AI install it

Copy this message into a VS Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server Stet for VS Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "servers": { "stet": { "type": "stdio", "command": "npx", "args": [ "-y", "stet-cli", "mcp" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Stet tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed

    Open the Node.js download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v

    Install once; it works for everything that needs Node.js

  2. Click this button to open VS Code

    Open in VS Code

    VS Code asks you to confirm; click Install

  3. Open the AI chat in VS Code in Agent mode

  4. Try it

    Use Stet and tell me what you can do for me, then show me one thing

    ✓ If VS Code says it is using Stet or shows a Stet tool in the answer, you are connected

Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.

See every app that uses MCP →

JSON settings are under “For developers” below

Stuck? Ask people who use Stet💬 Discussion →
For developers: Terminal commands and JSON settings

Installed on your computer

Claude Code

claude mcp add --scope user stet -- npx -y stet-cli mcp

Claude Desktop (claude_desktop_config.json)

{
  "mcpServers": {
    "stet": {
      "command": "npx",
      "args": [
        "-y",
        "stet-cli",
        "mcp"
      ]
    }
  }
}

Cursor (~/.cursor/mcp.json)

{
  "mcpServers": {
    "stet": {
      "command": "npx",
      "args": [
        "-y",
        "stet-cli",
        "mcp"
      ]
    }
  }
}

VS Code (mcp.json)

{
  "servers": {
    "stet": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "stet-cli",
        "mcp"
      ]
    }
  }
}

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

At a glance

Downloads per weeki
1,541/wk
Connection
Runs on your computer
Latest versioni
0.6.5
Published to registryi
Nov 15, 2026
Code last changedi
Nov 19, 2026
Maker
shamazkhan
Packages
npm: stet-cli
Registry status
Active

Which apps can use it

Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.

Run on your computer in

ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast

All apps, with pros and cons →

Related guides

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 19, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account shamazkhan, which owns the repo

  • ✓ Pass

    Still maintained

    Code last changed today

  • ✓ Pass

    Has a licence

    Uses MIT

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Published vulnerabilities (OSV.dev)

Not checked yet

What we check → · JSON

Makers: ask for a re-check or report wrong info
For makers: add a badge to your README

If you made this, paste this code into your README. The badge links back to this page.

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/shamazkhan-stet.svg)](https://mcp.popnx.com/en/servers/shamazkhan-stet)

Discussion

Ask, share a tip or report that it does not work. Sorted by what people marked helpful.

No posts yet. Be the first to ask or share.

Posts here are written by users, not the PopNx team.

Sign in to post

User reviews

No reviews yet

Sign in to write a review

Compared with others in Developer toolsi

  • More stars than 0% of the other 6116 servers in this category
  • Published to the registry more recently than 90% of the other 6116 servers in this category
  • Basic checks equal to or better than 99% of the other 6116 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Stet safe?

It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed today, and the latest version (0.6.5) reached the registry 4 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: GitDiagram, Appllama, Cloudflare MCP, Omnara, Repowise

Similar alternatives

Same category, other makers, commands already checked. Official ones first, then by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

GitDiagram

Architecture diagrams, explanations and Mermaid source for public GitHub repositories.

by ahmedkhaleel2004Widely used★ 19KUpdated 2 months ago

Runs in the cloud✓ service owner · gitdiagram.comTried by the PopNx team

Appllama

Study screens, flows and paywalls from top-earning iOS apps, then build from what wins.

by AppllamaWidely used★ 5.2KUpdated 3 months ago

Runs in the cloud✓ service owner · appllama.io

Repowise

Codebase intelligence for AI coding agents: graph, git history, docs, decisions, code health.

by repowise-devWidely used↓ 6.5K/wk★ 8.2K Stars for the whole repoUpdated 6 days ago

Computer or cloud✓ service owner · repowise.dev
Compared with similar ones
This one
Stet
GitDiagramAppllamaCloudflare MCPOmnaraRepowise
Runs whereInstalls on your computerRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to installCloud or install on your computer
Needs a keyNoNoNoNoNoNo
Add with + in ClaudeNoNoNoYesNoNo
Basic checks3/34/44/44/44/45/5
LicenseMITMITMITApache-2.0Apache-2.0AGPL-3.0
PriceNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registry

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

Stet: guardrails for AI coding agents

Stop AI coding agents from breaking what already works. · Website and docs: getstet.dev · Guides

Stet is a free, open-source CLI and MCP server for teams using Claude Code, Cursor, Codex, GitHub Copilot, Windsurf, Gemini CLI, ChatGPT or Claude. You set the scope of each AI task, lock the behaviours that must keep working, and Stet blocks any change that goes outside the task or breaks a lock. It works the same with every tool, and the agent can read the rules but can't rewrite them.

npx stet-cli init      # in any git repo; Node 18+

Use it when your AI agent "tidies" files outside the task, breaks a feature you thought was safe, quietly edits a failing test, ignores your AGENTS.md / CLAUDE.md / Cursor rules, or forgets the project between chats.

  • Charter → `AGENTS.md`. Write your product context and do's and don'ts once in .stet/charter.md. Stet keeps AGENTS.md (read by Codex, Cursor, Copilot and others) and CLAUDE.md in sync.
  • Locked behaviours. Lock what already works, each with a command that proves it. stet check runs them all. If one fails, the AI fixes its change, not the test.
  • Snapshot locks. Lock the *output* of a command (an export file, a list of API routes, mapped integration data). If it changes, stet check fails with a diff; stet lock approve accepts an intended change and logs why. No test file needed.
  • Scope guard. Agree the task and the files it may touch. stet guard flags every file changed outside scope or in protected paths, even if the agent already committed it.
  • Git-synced context. stet context builds a context pack from the live repo (charter, scope, locks, decisions, commits, uncommitted changes, file tree and the files you choose). Paste it into any chat instead of uploading your src folder.
  • Decision log. stet decide records "we chose X because Y", so the next session doesn't reopen it.
  • Linear tickets. stet scope set LIN-142 --allow "…" pulls the ticket's title and description from Linear into the context pack, so your AI gets the ticket and the code in one paste.
  • Ticket-aware PRs. Put the ticket ID in the scope (LIN-142 Add CSV export) and stet pr writes the commit message and PR description from the real diff, scope, check results and decisions. The git hook adds the ticket ID to every commit.
  • Repo study. stet study "checkout" maps how a part of the code works: key files, the files they depend on, entry points (routes), an import-flow diagram, the tests that cover it and what protects it. It writes docs/flows/checkout.md, keeps your own notes on refresh, and tells you when the code has changed since.
  • Handoff pack. stet handoff writes an onboarding document for a new developer or CTO, built from the repo.
  • MCP server. stet mcp exposes all of this as tools to Claude Code, Cursor and any MCP client.

No account. No telemetry. Your code never leaves your machine. Zero dependencies. Node 18+. Network calls are limited to two: once a day, when you run Stet in a terminal, it asks npm for the latest version number so it can offer an update (no code or repo information is sent; off in CI, or with STET_NO_UPDATE_CHECK=1). And if you set LINEAR_API_KEY, stet ticket fetches the Linear ticket you name (only the ticket ID is sent).

Install

npm install -g stet-cli        # or run any command with: npx stet-cli <command>

cd your-project stet init

stet init detects your stack and test command, then creates:

.stet/

charter.md what this is, stack, always / never rules ← edit this config.json name, protected paths, ignore globs locks.json locked behaviours scope.json current task scope decisions.md decision log AGENTS.md generated working agreement (your own text outside the stet block is kept) CLAUDE.md imports AGENTS.md for Claude Code

Commit .stet/, AGENTS.md and CLAUDE.md. Every agent and teammate then works from the same rules.

The loop

# once: lock what already works

stet lock add "Login works" --cmd "node --test test/auth.test.js" --protect "src/auth/**"

before each AI task (the ticket ID is optional)

stet scope set "LIN-142 Add CSV export" --allow "src/export/**,test/export*" stet context --files "src/export/**" # copied to clipboard; paste into your chat

after the AI says it's done

stet guard # anything outside scope or in protected paths? stet check # do all locked behaviours still pass?

ship it

stet pr # commit message + PR description (PR copied to clipboard) git commit -F .stet/.cache/commit.txt # "LIN-142: Add CSV export" + file list

Example output:

$ stet guard

Guarding 4 changed files (changes since 12b672b) · task: Add CSV export ✗ migrations/002_export.sql out of scope protected ✓ src/export/csv.js ✗ src/auth/session.js out of scope affects L2 ✓ test/export.test.js

✗ 2 files outside scope or protected. Revert, or widen the scope on purpose. ! Changes touch locked behaviour L2. Run: stet check --only L2

$ stet check Checking 2 locked behaviours ✗ L2 Login works (0.1s) │ not ok 1 - session expires after 30 minutes │ expected: 1800 │ actual: 0

✗ 1 locked behaviour broken: L2. Fix the change, not the check.

Snapshot locks

Many regressions are behaviour changes nobody wrote a test for: an export's column order, a renamed route, a mapping that shifted. Snapshot locks catch them with a tiny script that prints the behaviour:

stet lock add "Export format is stable" --snapshot "node scripts/export-sample.js" --protect "src/exports/**"

stet lock add "API routes unchanged" --snapshot "node scripts/print-routes.js" stet lock add "Report totals" --snapshot "python scripts/report.py" --mask "\d{4}-\d\d-\d\dT[\d:.]+Z"

Stet saves the output to .stet/snapshots/ as the approved version (commit it). From then on:

$ stet check

✗ L3 Export format is stable (0.2s, snapshot) │ output differs from the approved snapshot (- approved, + now): │ @@ line 1 @@ │ - id,name,email │ + id,email,name │ intended? approve it: stet lock approve L3 --why " "

  • Intended change? stet lock approve L3 --why "PRO-91: email column first" saves the new output and logs a decision.
  • Volatile output (timestamps, generated IDs)? Add --mask " "; matches become .
  • Tampering: stet guard flags any snapshot file edited by hand instead of through stet lock approve, and AGENTS.md tells agents never to approve snapshots themselves.
  • Keep snapshot scripts deterministic: fixed sample data, sorted output, no network.

Commands

CommandWhat it does
stet init [--name X] [--mcp]Set up .stet/, AGENTS.md and CLAUDE.md. --mcp also writes .mcp.json. Safe to re-run.
stet syncRegenerate the Stet block in AGENTS.md (other commands do this automatically).
stet scope set " " --allow " " [--ticket LIN-142]Agree the task and the files it may touch. Records the current commit as the base. A ticket ID at the start of the task is picked up automatically.
stet scope set … --strictRefuse to start a scope while there are uncommitted files. Without it, earlier uncommitted work is *carried*: guard ignores it unless it changes again.
stet scope carry / --allMark files guard flagged as leftovers from before the scope.
stet scope done [--commit] [--force]Run guard and check, commit only the task's files (with the stet pr message) and close the scope.
`stet scope [show\clear\ticket]`Show or clear the scope, or print just the ticket ID.
stet guard [--staged] [--base ref] [--warn]Check changes since the scope base (committed, staged, unstaged and untracked). Exits 1 on violations unless --warn.
stet lock add " " --cmd " " [--protect " "]Lock a behaviour. --protect tells guard which files affect it. A command that is already locked is refused (--force to add anyway).
stet lock rename L1 " "Rename a lock, e.g. the test-suite lock stet init creates.
stet lock add " " --snapshot " " [--mask " "]Lock a command's output as an approved snapshot in .stet/snapshots/.
stet lock approve L3 --why " "Accept a changed snapshot on purpose; logged as a decision.
`stet lock [list\rm L2]`List locks with their last result, or remove one.
stet check [--only L1,L2]Run locked behaviours. Exits 1 if any fail and shows the failing lines.
`stet context [--files " "] [--changed] [--diff] [--copy\--stdout\--out f]`Build the context pack. By default it writes .stet/context.md and copies it to the clipboard.
stet decide " " [--why " "]Add to the decision log.
stet decisions [--all]List decisions.
stet ticket [LIN-142] [--stdout] [--cached]Fetch a Linear ticket (needs LINEAR_API_KEY). It is included in stet context and linked in stet pr. With no ID, shows the current scope's ticket.
stet pr [--base main] [--check] [--stdout]Write .stet/.cache/commit.txt and .stet/.cache/pr.md from the diff since the scope was set: ticket, changed files, scope result, stet check results and decisions logged during the task. --check runs the locks first.
stet study " " [--out file] [--max 12]Map a flow: key and supporting files, routes, Mermaid diagram, tests, protection gaps. Writes docs/flows/ .md.
stet studyList studied flows and which are out of date.
stet context --flow Context pack with the flow doc and all its files.
stet handoff [--out HANDOFF.md] [--stdout]Generate the onboarding pack.
stet hook install [--check]Add git hooks: pre-commit blocks commits that stage out-of-scope or protected files (--check also runs stet check); prepare-commit-msg adds the ticket ID to commit messages.
stet update [--yes]Check for a newer release and install it (asks first unless --yes).
stet badge [--add]Print the "guarded by stet" README badge, or add it to your README.
stet statusOne-screen summary.
stet mcp / stet mcp installRun the MCP server over stdio, or write .mcp.json.

Add --json to any command for machine-readable output.

Repo study

Took over a codebase, or about to change a part you don't know well?

stet study "checkout"

Writes docs/flows/checkout.md from the code itself:

  • Entry points: routes that lead into it (Express, Fastify, FastAPI, Flask, NestJS, Django path())
  • Flow: a Mermaid diagram of which file uses which (GitHub renders it)
  • Key files and the supporting files they depend on, with their main functions
  • Tests that cover it, and what protects it (locks, protected paths), with suggested stet lock commands for the gaps
  • Recent changes and related decisions

Then get the explanation from your AI:

stet context --flow checkout   # the flow doc + all its files, copied to your clipboard

The doc includes a ready prompt. Paste the answer into its How it works section: Stet keeps that section and your Notes when you refresh the doc. stet study on its own lists your flows and flags the ones whose code changed since they were written; stet status

Only the beginning is shown; read the rest in the repo