StormixStormix/transcripts-mcp/.agents/skills/calldiff/SKILL.md

calldiff

Skill8 starsChanged 2 months agoMITView on GitHub

Generate call-stack diffs with `npx calldiff@latest` and include them when writing a plan, design doc, ADR, PR description, commit body, or summary of a code change, so reviewers can see how call flow changed. Use whenever a change rewires who-calls-whom and a line diff would bury the shape of the change.

2 other projects use a version of this.

Adopted by

Most recently taken up by

deadlock-mod-manager/deadlock-mod-managertheir own version, first seen Nov 1, 2026
humanlayer/humanlayertheir own version, first seen Oct 25, 2026

Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
humanlayer/humanlayer★ 13ksame name
deadlock-mod-manager/deadlock-mod-manager★ 584same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository33 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .deepsec/AGENTS.mdAGENTS.md
- .cursor/rules/010-workflow.mdcCursor rule
- .cursor/rules/020-codebase-structure.mdcCursor rule
- .cursor/rules/030-coding-style.mdcCursor rule
- .cursor/rules/031-never-use-any.mdcCursor rule
- .cursor/rules/032-import-rules.mdcCursor rule
- .cursor/rules/050-testing.mdcCursor rule
- .cursor/rules/070-comments-defensive-programming.mdcCursor rule
- .cursor/rules/080-ai-interaction.mdcCursor rule
- .cursor/rules/090-changesets.mdcCursor rule
- .cursor/rules/095-calldiff.mdcCursor rule
- .cursor/rules/990-cursor-rule-editing-workaround.mdcCursor rule
- .cursor/rules/999-mdc-format.mdcCursor rule
- adversarial-reviewSkill
- agent-browserSkill
- changesetSkill
- commitSkill
- deslopSkill
- fix-prSkill
- git-conventionsSkill
- humanizerSkill
- improve-codebase-architectureSkill
- logging-best-practicesSkill
- opensrcSkill
- rebaseSkill
- recomposing-commitsSkill
- security-reviewSkill
- show-meSkill
- simplifySkill
- thermo-nuclear-code-quality-reviewSkill
- wait-whatSkill
- writing-for-agentsSkill

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific

Very specific:
When documenting a change to control flow, generate a call-stack diff with npx calldiff@latest and paste it next to the prose it supports.
line 8

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.

Files

SKILL.md

Call-stack diffs with calldiff

When documenting a change to control flow, generate a call-stack diff with npx calldiff@latest and paste it next to the prose it supports. Line diffs bury who-calls-whom; the ASCII tree is what reviewers need.

For choosing a call tree over other visuals, see show-me.

When to use

Include a calldiff in any plan, design doc, ADR, PR description, commit body, or chat summary that describes a change to control flow.

Skip it for content, config, docs, or edits that leave call flow untouched.

Commands

HEAD vs working tree:

npx calldiff@latest diff

One ref vs working tree, or two refs:

npx calldiff@latest diff main
npx calldiff@latest diff --from main --to feature

Pin entrypoints and scope to a package in this monorepo:

npx calldiff@latest diff -e createLogger -e ClassName.method -- packages/core
npx calldiff@latest diff -F packages/core/src/index.ts

Current shape (no diff) and path questions:

npx calldiff@latest tree -e createLogger
npx calldiff@latest reach -e createLogger --to emit

Optional flags: --locs for call-site file:line, --format json|yaml|md|jsonl for structured output.

How to include the output

Paste the ASCII tree in a diff fenced block next to the prose it supports. Trim to the entrypoints a reviewer cares about; do not dump full depth.

 submitForm
   createSession
     persistPrompt
+    expandSkillMention
     launchAgent
-  navigateToSession
+  navigateToSession
+    subscribeToEvents

Limits

Syntactic only: dynamic and indirect calls do not resolve.
Requires committed or working-tree-resolvable code. Grammars download on first use.
Hand-write the tree for hypothetical or unresolvable flow and label it as such.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

It worked
Partly
It didn't

What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free