Skill

flow-config

Displays current FLOW configuration from .flow.json including version and per-skill autonomy settings (commit/continue) in a table. Useful for verifying project FLOW setup via /flow:flow-config.

developer-tools

npx claudepluginhub benkruger/flow

Tool Access

This skill uses the workspace's default tool permissions.

Preview

```text

SKILL.md

Similar Skills

flow-prime

Initializes FLOW projects by configuring workspace permissions, git excludes, installing bin stubs, setting skill autonomy levels, and committing changes. Run once after install or upgrade.

flow

Config

Provides context and instructions for config.md files in Claude Code, useful when configuring skills, settings, or project options.

1 file

eidos

setup-skill-discovery

Generates .dh/skill_discovery.yaml by scanning repo for tech stack signals like pyproject.toml and package.json, inventorying skills via npx skills list, suggesting candidates, and writing config for skill injection.

4 files

Stats

Stars15

Forks0

Last CommitApr 11, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

FLOW Config — Display Configuration

Usage

/flow:flow-config

Display-only skill. Reads .flow.json from the project root and shows the current configuration.

Steps

Step 1 — Read config

Use the Glob tool to check for .flow.json at the project root.

If .flow.json does not exist, tell the user:

"No .flow.json found. Run /flow:flow-prime to configure this project."

Stop here.

If .flow.json exists, read it with the Read tool.

Step 2 — Display config

Output the following banner in your response (not via Bash) inside a fenced code block:

```text
──────────────────────────────────────────────────
  FLOW v<version> — Config
──────────────────────────────────────────────────
```

Then display the skills configuration as a markdown table:

| Skill     | Commit | Continue |
|-----------|--------|----------|
| start       | —      | manual   |
| plan        | —      | auto     |
| code        | manual | manual   |
| code-review | auto   | auto     |
| learn       | auto   | auto     |
| complete    | auto   | —        |
| abort       | auto   | —        |

Use the actual values from .flow.json. The table above is just an example.

Column rules:

Phase skills with both axes (code, code-review, learn): show both commit and continue values from the nested object
Phase skills with continue only (start, plan): show — for Commit, show the continue value
Utility skills (complete, abort): show the single string value under Commit, show — for Continue

Legacy format handling: If .flow.json has the old single-value format (e.g., "code": "manual" instead of {"commit": "manual", "continue": "manual"}), display the single value in both columns for phase skills that should have two axes.

If .flow.json has no skills key, show "No skills configured — using built-in defaults" instead of the table.

Tell the user that phase skills can be overridden at invocation time with flags controlling autonomy.

Hard Rules

Display only — never modify .flow.json
Never use Bash to print banners — output them as text in your response
Never use Bash for file reads — use Glob, Read, and Grep tools instead of ls, cat, head, tail, find, or grep
Never use cd <path> && git — use git -C <path> for git commands in other directories
Never cd before running bin/flow — it detects the project root internally