Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
athola avatar

Workflow Diagram

  • 78 installs
  • 325 repo stars
  • Updated August 2, 2026
  • athola/claude-night-market

Workflow Diagram is an agent skill that generates Mermaid flowcharts of pipelines and state transitions after a structured codebase exploration pass.

About

Workflow Diagram is an agent skill for solo builders who need trustworthy visuals of how work moves through their repo—deployment pipelines, git hook chains, Makefile targets, or application lifecycle states—without hand-drawing boxes that drift from reality. It prescribes a disciplined two-step flow: dispatch a codebase explorer scoped to process steps, conditionals, and transitions, then translate that structural model into Mermaid with shape semantics that distinguish decisions, subprocesses, and sync points. Frontmatter positions it for CI/CD and lifecycle documentation when someone asks what runs in what order. The skill is generator-shaped documentation aid, not a diagram hosting service; output is paste-ready Mermaid for wikis, PRs, or internal docs. Intermediate complexity reflects agent orchestration plus graph design rules. Use when prose runbooks fail and you want a living map anchored in actual config and entrypoints.

  • Two-step workflow: codebase explorer agent first, then Mermaid syntax generation
  • Supports flowchart TD for sequences and LR for parallel pipeline tracks
  • Shape vocabulary: rectangles, diamonds, stadium start/end, subroutines, join circles
  • Explicit triggers: Makefiles, CI configs, hook chains, lifecycle methods
  • Subgraph grouping for parallel tracks and labeled transition edges

Workflow Diagram by the numbers

  • 78 all-time installs (skills.sh)
  • Ranked #699 of 1,879 Documentation skills by installs in the Skillselion catalog
  • Security screen: LOW risk (skills.sh audit)
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/athola/claude-night-market --skill workflow-diagram

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs78
repo stars325
Security audit3 / 3 scanners passed
Last updatedAugust 2, 2026
Repositoryathola/claude-night-market

What it does

Produce accurate Mermaid flowcharts of CI/CD pipelines, hook chains, and state machines by exploring the repo then rendering decision and process nodes.

Who is it for?

Best when you're documenting deploy or release flows, onboarding contributors, or answering “what happens when this command runs?” from the actual tree.

Skip if: One-line scripts with no branching, teams that already maintain canonical diagrams in a dedicated diagram-as-code repo with no drift, or purely aesthetic UI mockups.

When should I use this skill?

Use when documenting CI/CD pipelines or lifecycle processes.

What you get

You get a Mermaid flowchart with typed nodes, labeled edges, and optional subgraphs that mirrors Makefile, CI, and hook logic discovered in the repo.

  • Mermaid flowchart source
  • Structured list of process steps and decision points

By the numbers

  • Documented workflow has 2 main steps: explore codebase, then generate Mermaid syntax
  • Diagram rules cover 5 distinct Mermaid node shape types for process, decision, start/end, subroutine, and join

Files

SKILL.mdMarkdownGitHub ↗

Workflow Diagram

Generate a Mermaid flowchart showing process workflows, pipelines, or state machines from code or documentation.

When To Use

  • Visualizing CI/CD or deployment pipelines
  • Documenting multi-step development workflows
  • Mapping state machines or lifecycle processes
  • Answering "what steps happen when X runs?"

Workflow

Step 1: Explore the Codebase

Dispatch the codebase explorer agent:

Agent(cartograph:codebase-explorer)
Prompt: Explore [scope] and return a structural model.
Focus on process steps, conditional logic, state
transitions, and pipeline stages for a workflow diagram.
Look for: Makefiles, CI configs, hook chains, command
sequences, and lifecycle methods.

Step 2: Generate Mermaid Syntax

Transform the structural model into a Mermaid flowchart with decision nodes and process steps.

Rules for workflow diagrams:

  • Use flowchart TD for sequential processes
  • Use flowchart LR for pipelines with parallel tracks
  • Use shapes to distinguish step types:
  • [Rectangle] for process steps
  • {Diamond} for decision points
  • ([Stadium]) for start/end states
  • [[Subroutine]] for sub-processes
  • ((Circle)) for join/sync points
  • Use -->|label| for transition conditions
  • Group parallel tracks into subgraphs
  • Color-code by outcome:
  • Default for happy path
  • Dotted (-.->) for error/fallback paths
  • Thick (==>) for critical path
  • Limit to 20 nodes maximum

Example output:

flowchart TD
    start([Start: PR Created])
    lint[Run Linters]
    test[Run Tests]
    review{Code Review}
    approve[Approved]
    changes[Request Changes]
    merge([Merge to Main])

    start --> lint --> test
    test --> review
    review -->|pass| approve --> merge
    review -->|fail| changes -.-> lint

Step 3: Render via MCP

Call the Mermaid Chart MCP to render:

mcp__claude_ai_Mermaid_Chart__validate_and_render_mermaid_diagram
  prompt: "Workflow diagram of [scope/process]"
  mermaidCode: [generated syntax]
  diagramType: "flowchart"
  clientName: "claude-code"

If rendering fails, fix syntax and retry (max 2 retries).

Step 4: Present Results

Show the rendered diagram with a brief description of the workflow stages and decision points (2-3 sentences).

Exit Criteria

  • [ ] Mermaid flowchart syntax generated containing at least one

diamond {Decision} node representing a conditional branch

  • [ ] mcp__claude_ai_Mermaid_Chart__validate_and_render_mermaid_diagram

called and returns without error (or retry attempted and result reported)

  • [ ] Error/fallback paths rendered as dotted arrows (-.->) distinct

from happy-path arrows when error paths exist in the source

  • [ ] Node count is at most 20; if more steps exist, sub-processes

are collapsed into [[Subroutine]] nodes

  • [ ] A 2-3 sentence description of workflow stages and decision

points is shown alongside the diagram

Related skills

How it compares

Repo-grounded Mermaid generation via exploration—not a generic whiteboard prompt or architecture-only C4 skill.

FAQ

Who is workflow-diagram for?

Developers who ship with CI/CD or multi-step automation and need diagrams that match the repository, not generic templates.

When should I use workflow-diagram?

In build/docs when onboarding or ADRs need a pipeline map, in ship/launch when explaining release gates, and in operate/infra when documenting lifecycle or recovery sequences.

Is workflow-diagram safe to install?

The skill instructs agents to read your codebase; review the Security Audits panel on this page and scope explorer access to directories you are comfortable exposing.

Documentationdocsdevops

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.