fix: quote the plugin path in the validate_layers.dart command
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 85/100
Research direction
Read agents/ffca-layer-auditor.md around line 39 and skills/ffca-audit/SKILL.md around lines 27 and 30. Quote the plugin script path in each documented command so paths containing spaces work. Review all three commands and confirm the quoting is consistent; the issue says the plugin-paths CI job could also catch unquoted references.
Written by the indexing model from the issue text.
Description
Description
The ffca-layer-auditor agent and the ffca-audit skill tell the model to run:
dart run ${CLAUDE_PLUGIN_ROOT}/scripts/validate_layers.dart --all
Claude Code substitutes the installed plugin path into that text.
When the path has a space, the command splits and dart run gets the wrong file.
claude plugin validate only checks hook files for this, so CI won't flag it.
It appears in:
agents/ffca-layer-auditor.md, line 39skills/ffca-audit/SKILL.md, lines 27 and 30
Steps To Reproduce
- Load the plugin from a path with a space, e.g. the Claude desktop app on macOS (
~/Library/Application Support/Claude/…). - Run the
ffca-auditskill in an FFCA repo. - The auditor runs the command as written, and
dart runcan't find the script.
Expected Behavior
The validator runs from any install path.
Quoting fixes it:
dart run "${CLAUDE_PLUGIN_ROOT}/scripts/validate_layers.dart" --all
Additional Context
- I haven't reproduced it. The model may quote the path on its own, but nothing tells it to.
- https://code.claude.com/docs/en/plugins-reference: "In skill, command, and agent content, write the
${...}reference in the Markdown body instead, and Claude Code substitutes the path inline when it loads the content." - The
plugin-pathsCI job could also fail on an unquoted${CLAUDE_PLUGIN_ROOT}in a command. - Same root cause as VeryGoodOpenSource/vgv-ai-flutter-plugin#194, there in a hook.
- Dominant language
- Dart
- Stars
- 7
- Forks
- 2
- Avg merge
- 9h 59m
- Merged PRs (30d)
- 7
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from VeryGoodOpenSource/vgv-ffca-plugin
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
chore
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
chore
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 76/100
-
feature
Difficulty 3/5 1-2 days Newbie friendliness 48/100
All issues in VeryGoodOpenSource/vgv-ffca-plugin
Similar issues
-
good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
StabilityNexus/Zplit#77 · 1 comment ·
-
🚀 [firebase_core] Bump Firebase C++ SDK (14.1.0 → 14.2.0)Possibly taken @SelaseKay claimed this today. OpenNeeds Attention type: enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
firebase/flutterfire#18977 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
-
agent: is checked on a wrapper holding several checkables answers from the first one in tree orderOpenbug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
AlphaWaveSystems/flutter-probe#865 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
ubuntu/app-center#2306 ·
Maintainers usually reply within 1 day