Rupali59

Propagate Why — Development skill for Claude Code

Development community

Find out why one file is declared to follow another, and what verified it last.

How to install Propagate Why

Installs to ~/.claude/skills/rupali59-propagate-propagate-why/SKILL.md

Terminal
mkdir -p ~/.claude/skills/rupali59-propagate-propagate-why && curl -fsSL https://raw.githubusercontent.com/Rupali59/propagate/HEAD/commands/propagate-why.md -o ~/.claude/skills/rupali59-propagate-propagate-why/SKILL.md

Restart Claude Code, or start a new session, for it to be picked up.

What Propagate Why does


allowed-tools: Bash(node "${CLAUDE_PLUGIN_ROOT}/cli.mjs" why:*) description: Find out why one file is declared to follow another, and what verified it last

Your task

Run the command below for the edge the user names. It needs an edge id:

node "${CLAUDE_PLUGIN_ROOT}/cli.mjs" why  [--all] [--json]

If the user gave a file rather than an edge id, run `propagate status` or `reconcile` first to find the id, then come back.

Report the declared reason (`why`) and the ver

Alternatives in Development

  • Create Handoff — You are tasked with writing a handoff document to hand off your work to another agent in a new session 10k ★
  • Claude Code Sub Agent Collective — 🧠 Context Engineering Research - Not just another agent collection, but using research and context engineerin 523 ★
  • Copilot Leak — Copilot's auto-review escapes: find them since the last look, sanitise them, and turn each one into a lesson 189 ★

Full documentation available on GitHub

View Source Repository