code-flow-quality

Code Flow — Quality Report

Read the map this project has already written under Code_Flows/ and report where it shows duplicated intent, needless complexity, code that nothing reaches, responsibilities and dependencies that sit wrong, and modules whose interface costs a caller more than the implementation behind it hides.

This skill never edits source code. code-flow-map adds missing docstrings as it traces; this one writes documents and stops. Consolidating duplicates and deleting suspected-dead code carry real blast radius, and that call is the user's.

User Input

The user's request carries two optional flags, --read-code and --rules. Step 1 reads them.

Instructions

Follow these steps exactly.

1. Read the Arguments

The user's request carries two optional flags:

• --read-code — after deriving candidate findings from the map, open the files those candidates cite and confirm each against current source. Off by default. It requires the source tree to be present and current, not merely the artifacts under Code_Flows/. It also decides two of step 3's detectors outright: open-closed and liskov-substitution cannot be settled from the map and do not run without it.
• --rules [source ...] — also check the map against rules this project has already written down. Off by default. A source is a path to a document, the word auto, or a rule written inline in quotes; several may be given, separated by spaces or commas, and --rules with no value means auto. Step 2 loads them and step 3's last detector checks them. This is how a project's own standard — a CLAUDE.md, an AGENTS.md, a Spec Kit constitution, a team style guide — gets reported with the same evidence and the same honesty as DRY, KISS and YAGNI, instead of being a thing everyone agreed to and nobody checks.

There is no feature name to parse: this command analyzes the whole map. If the input contains anything else, say what you read, ignore it, and carry on — do not treat it as a filter, a path, or a flow name.