flow-next-map

Wraps the clawpatch CLI to build a semantic feature index of a repository.

692|55|Updated Dec 26, 2025
One-click install
npx skills add https://github.com/gmickel/gmickel-claude-marketplace --skill flow-next-map
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: flow-next-map
Source: https://github.com/gmickel/gmickel-claude-marketplace/tree/main/plugins/flow-next/codex/skills/flow-next-map
Command: npx skills add https://github.com/gmickel/gmickel-claude-marketplace --skill flow-next-map

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires clawpatch.

What problem does it solve?

Understanding a large or unfamiliar codebase is slow when you have no map of its features. This Skill wraps the clawpatch CLI's map subcommand to generate a semantic feature index of your repository, producing Zod-validated JSON feature files under .clawpatch/features/ that downstream planning and capture workflows can consume.

Core Features & Use Cases

  • Provider-free heuristic mapping: Runs clawpatch map with --source heuristic by default, using zero LLM calls and zero API spend for a deterministic filesystem-based index.
  • Install detection and version guard: Detects a missing clawpatch binary and prints pnpm install instructions, and warns (without blocking) when the installed version falls outside the supported >=0.4.0 <0.5.0 range.
  • Local-only sharing contract: Writes a self-contained .clawpatch/.gitignore skeleton so the feature index stays local per developer and never creates PR review noise.
  • Use Case: You join a new repo and want a quick feature inventory before planning work. Run the map skill, get a count of detected features with a last-mapped timestamp, then feed the index into /flow-next:plan or /flow-next:capture.

Quick Start

Ask the assistant to map the repository with the flow-next map skill, optionally passing --source auto or --source agent for LLM-backed mapping when heuristic coverage is weak.

Frequently Asked Questions about flow-next-map

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a feature map of my repository?

Run the flow-next map skill, which invokes clawpatch map --source heuristic by default. The deterministic mapper walks the filesystem and writes Zod-validated feature JSON files to .clawpatch/features/ with no LLM calls or API spend.

How do I install clawpatch for repository mapping?

Install clawpatch globally with pnpm add -g clawpatch, which requires Node 22 or later. The skill never auto-installs; it detects a missing binary, prints the install command, and hints at running pnpm setup if the global bin directory is not on your PATH.

Why did heuristic mapping find zero features in my repo?

The heuristic mapper targets conventional app and framework layouts, so CLI tools, plugins, docs-heavy repos, and non-standard monorepos may map to zero features. Re-run with --source auto or --source agent for LLM-backed mapping, which requires a configured CLAWPATCH_PROVIDER.

Does the feature index get committed to git?

No. The skill writes a .clawpatch/.gitignore skeleton that ignores everything under .clawpatch/ except the .gitignore itself, keeping the index local per developer. Teams can opt into sharing by editing that file, but this is unsupported.

What happens if my clawpatch version is outside the supported range?

The skill supports clawpatch >=0.4.0 <0.5.0. An outside-range version triggers a single stderr warning naming expected versus found versions, and the map still runs; the guard degrades rather than blocking because clawpatch is pre-1.0.

Can the map skill run in autonomous or headless loops?

No. The skill declines to run when REVIEW_RECEIPT_PATH or FLOW_RALPH signals are set, exiting with code 2, because install and init paths may require interactive user consent that autonomous loops cannot provide.