Repository navigation
docs: data-flow reports in the skill, site and code map - #400
Merged
Merged
Conversation
Fold the reading rules of tsx-data-flow's render-path-dataflow-work skill into srcly-code-quality, document report/compare --dataflow and the two data-flow finding rules on the site, add the Data flow metrics to the site catalog, and record M7's state in the initiative map. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The
srcly-code-qualityskill now says how to run and read the data-flow report, and the site documents--dataflow,dataflow.mdand the two data-flow finding rules. This folds tsx-data-flow'srender-path-dataflow-workreading rules into srcly.What to do with it
Reference only. M7 stays open in the initiative map: the context-relay and broad-prop-bundle rules and an in-app trigger are left, so the plan is not retired.
Proof
skills/srcly-code-quality/SKILL.md, from the old skill's reading rules (Feature Clusters evidence, Grouped Recommendations, Pack verdict, Extraction shape check,mergePropsdefaults, SVG shell values, Background Findings, Provider/Context completion, Stop Recommendation). The old CLI commands and flags are left out; srcly's commands replace them.cli.md,reports.md,findings.mdanddata-flow.mddescribe the behavior shipped in feat: srcly report --dataflow, data-flow metrics and code-viewer marks #399.site/src/data/catalog.jsonadds the six Data flow metrics from the catalog payload on this branch (additions only;capture.mjswill rewrite it frommainnext time).docs/CODE_MAP.mdgets the data-flow signals row; the initiative map records M7 as active with what is left.Survey moves: none from this layer (docs only); the stack's server moves are explained in #398 and #399.
Stack: data-flow reporting, layer 3 of 3
This slice: skill, site pages, site catalog, code map and initiative map.
Why it is its own layer: Docs describe the shipped behavior and can change without touching code.
Full story: #398
🤖 Generated with Claude Code