本文へ移動
cccskills
無料GitHub で公開

map-flows

Use when asked to map or analyze flows, pipelines, processes, or sequences of events in this repo — e.g. "mapa el flujo", "flow", "pipeline", "ciclo de vida", "trace the request", "how does the build/release flow work", "diagrama del flujo". Maps data flows, request lifecycles, CI/CD pipelines, and state transitions with verified file:line evidence. Distinct from analyze-code (which maps code structure); this skill maps movement over time.

sazardev/networking-with-go
インストール方法を見る

含まれるファイル（1）

  • SKILL.md2.9 KB

SKILL.md（原文）

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Flow Mapper

You trace and diagram how things move through a system: data, requests, processes, CI/CD pipelines, and state. Every step in the flow is grounded in a real file or command — a flow map is only as good as its evidence.

Steps

  1. Identify the flow — is it data flow, a request lifecycle, a CI/CD pipeline, a state machine, or a build/release process? Ask if ambiguous, otherwise infer from the request and proceed.

  2. Find the entrypoint(s) mechanically — for a request/data flow: the listener, handler, or function that receives input. For a pipeline: the trigger (GitHub Actions: on: in .github/workflows/*.yml; web: the page that boots the JS; Go: main()). Read the entrypoint fully.

  3. Trace step by step — follow each hop from source to sink:

    • What invokes the next step (function call, event, HTTP request, message, workflow step, cron)?
    • What data is passed, transformed, or dropped at each hop?
    • Where does it branch, retry, or fail?
    • Where does it end (response, file, DB, deployment, terminal state)? For each hop record file:line evidence.

  4. Check the flows you cannot trace by reading — commands that prove behavior: run the pipeline dry (shellcheck, go vet, build), grep for the entrypoint callers, trace where a symbol/step is referenced. Note anything you had to infer rather than verify.

  5. Include failure paths — every flow has error paths; map what happens on each failure (retry, abort, fallback, silent). A flow map without failure paths is a fairy tale.

  6. Diagram and report — produce a step-by-step map. Use a text sequence (and offer Mermaid on request). Keep it precise, not decorative.

Output format

  1. Flow type and scope — what was mapped and from where to where.
  2. The map — numbered steps, each with: action, responsible component/file (file:line), data in -> data out, and trigger.
  3. Branches and failure paths — every conditional/error path with its outcome.
  4. Hot spots — steps that are fragile, slow, or risky (blocking I/O, fixed ports, no timeout, no retry, || exit 1 chains).
  5. Verified — commands run and results; anything inferred marked as such.
  6. Improvements (only if requested or glaring) — concrete, ordered.

Rules: evidence at every hop; distinguish verified from inferred; map the real flow, not the intended one.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

ログインしてレビューを書く

同じリポジトリのスキル

概要と使いどころ

analyze-code

無料

Use when asked to analyze a file, a directory, or the whole codebase to understand structure, architecture, dependencies, complexity, duplication, dead code, or technical debt — e.g. "analyze this", "análisis total", "explain this codebase", "mapa del código", "how does X work", "technical debt". Produces a complete, structured picture with verified commands, not guesses. Distinct from review-* skills (which judge quality); this skill explains and maps.

日本語の概要は準備中です。原文の説明を表示しています。

sazardev/networking-with-go582026年8月8日 更新

audit-security

無料

Use when asked to audit or harden security in this repo — e.g. "security audit", "auditoría de seguridad", "revisa la seguridad", "is this secure", "hardening", "vulnerabilities". Audits code, config, workflows, and secrets exposure. Covers injection, secrets, TLS, untrusted input, dependency risk, and CI supply-chain hygiene. Runs when the user asks about security, not just for code reviews.

日本語の概要は準備中です。原文の説明を表示しています。

sazardev/networking-with-go582026年8月8日 更新

book-flow-analyst

無料

Use when reviewing the structure, ordering, coherence, and narrative flow of the book as a whole or across chapters. Checks chapter sequencing against the ID scheme, cross-references and forward hooks between chapters, README/index link integrity, exercise-to-chapter pairing, duplicate or contradictory content, and progression of difficulty. Best paired with a full-docs review rather than a single-chapter proofread.

日本語の概要は準備中です。原文の説明を表示しています。

sazardev/networking-with-go582026年8月8日 更新

book-writer

無料

Use when writing, expanding, rewriting, or drafting any chapter (.mdx) or Go exercise for this book. Encodes the authorial voice, the mdx-pdf-format rules, the ID/naming scheme, the zero-emoji rule, chapter/exercise pairing, and the "theory first, then code" pedagogy so new or edited content reads like the rest of the book and keeps the PDF compiling.

日本語の概要は準備中です。原文の説明を表示しています。

sazardev/networking-with-go582026年8月8日 更新

design-ideas

無料

Use when brainstorming, evaluating ideas, designing architectures, writing technical plans, or choosing between approaches — e.g. "give me ideas", "ideas para", "diseña la arquitectura", "how should I structure this", "compare approaches", "plan". Turns vague ideas into concrete, prioritized, buildable designs with explicit tradeoffs. Use before writing code, not after.

日本語の概要は準備中です。原文の説明を表示しています。

sazardev/networking-with-go582026年8月8日 更新

english-grammar-reviewer

無料

Use when proofreading, copy-editing, or verifying English in any docs/**/*.mdx chapter or code comment in this repo. Catches grammar, punctuation, spelling, syntax, article/tense/agreement errors, wordiness, tone drift, and style inconsistencies, and rewrites text in the book's confident second-person voice without changing meaning or breaking the mdx/PDF format rules.

日本語の概要は準備中です。原文の説明を表示しています。

sazardev/networking-with-go582026年8月8日 更新

sazardev のスキルをすべて見る

このスキルの問題を報告する