agentsclimarketplace
Sign in

Code flow analysis

Skill jagreehal/jagreehal-claude-skills/skills/code-flow-analysis

Traces a code execution path with file:line references and an execution diagram before any change. Use this skill when about to fix a bug, implement a feature, refactor, or start a TDD cycle on non-trivial code. Do not use when/for pure design discussion without code (use design-exploration) or after a fix is already validated.From its SKILL.md

Install
npx -y skills add jagreehal/jagreehal-claude-skills --skill code-flow-analysis

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.9 KB, as published. Nobody here has run it

Code Flow Analysis

Critical rules

  • Trace before implementing non-trivial changes. No abstractions like "the handler" — use file:line.
  • Diagrams stay short (5-15 lines). Show fn(args, deps), Result ok/err, workflow steps, error mark.
  • Confirm understanding with the user before changing code.
  • Red flags: fix without file:line; adding retry/validation/cache without checking upstream; changing internals without callers; assuming Result is ok.
  • Before drawing examples or pattern-specific traces, read references/examples.md.

Workflow

  1. Trace: entry point, fn(args, deps) chain, error/change location, workflow steps, Result propagation — all with file:line.
  2. Draw a concise execution diagram (see examples).
  3. Verify: "Here's the flow: [diagram]. Error/change at [file:line] when [condition]. Correct?" Wait for confirmation.
  4. Only then implement (feeds debugging-methodology / tdd-workflow).

Resources

  • references/examples.md — diagram shape, Result/workflow traces, bug/feature examples, rationalizations. Read before tracing non-trivial flows.

Validation

  • Entry and full call chain with file:line
  • Result propagation and error/change location marked
  • Diagram concise (5-15 lines)
  • User confirmed understanding before code changes

Constraints

  • Skip for typos, formatting, docs-only.
  • Related: debugging-methodology, tdd-workflow, result-types, fn-args-deps, resilience, validation-boundary, confidence-levels.

Keep looking

Skills are one crate of 627,801. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.