Skip to content
Skills Library
Programming · Analysis

code-flow-analysis

/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.

Licence
MIT
Last repository change
30.07.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
2
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 30.07.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

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.

Original author description

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.

How it works

  1. Critical rules
  2. Workflow
  3. Resources
  4. Validation
  5. Constraints
Original SKILL.md headings · 34 lines, 194 words
SKILL.md preview
---
name: code-flow-analysis
description: >-
  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.
version: 1.2.0
---

# 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](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](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`.
Files in this package (2)
  • SKILL.md 2 KB
  • references/examples.md 2 KB

Versions

The database has no other skills named code-flow-analysis.

Database snapshot: 13.11.2026 · package version f53d3cf99d7a (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100tdd
    Test-driven development: red-green-refactor, one test per cycle. Use when the task asks to build a feature, fix a bug or change behaviour, before you write the code.
  • 96tdd-workflows-tdd-refactor
    Use when working with tdd workflows tdd refactor
  • 90dev-flow
    This skill should be used when the user asks to "start work on a feature", "fix this bug", "implement this ticket", or "work on this regression". Standard development flow for any code change — feature path (design interrogation, falsify, plan, worktree, build, verify, ship) or…
  • 90tdd-loop
    Use when you add or change behavior in code, or fix a bug. Runs the red, green, refactor cycle with a failing test first.
  • 96tdd-workflows-tdd-cycle
    Use when working with tdd workflows tdd cycle
  • 100clean-code
    This skill should be used when the user asks to "refactor code", "review code quality", "apply clean code principles", "check for code smells", "improve code design", "do a clean code review", "apply SOLID principles", "fix naming", "reduce complexity", or when performing the…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.