Skip to content

docs: fix marketplace install instructions and stale symlink claims - #93

Open
fege wants to merge 3 commits into
fullsend-ai:mainfrom
fege:fix-install-instructions
Open

fege wants to merge 3 commits into
fullsend-ai:mainfrom
fege:fix-install-instructions

Conversation

@fege

@fege fege commented Oct 28, 2026 •

Copy link
Copy Markdown
Collaborator

Summary

Docs-only fix for the marketplace install instructions and stale symlink claims.

  • Install: the old cd ~/.claude/plugins/test-plan && uv sync --extra dev step pointed
    at a path that doesn't exist (marketplace installs live in a versioned plugin cache) and
    wasn't needed — the skills bootstrap their own dependencies on first run (except
    /test-plan-ui-verify). Install block is now terminal-only claude plugin commands,
    with the in-Claude-Code /plugin install noted as an alternative.
  • Symlinks: the repo has no symlinks and no skills/_common/; skills reach the
    plugin-root scripts/ via relative paths (${CLAUDE_SKILL_DIR}/../../scripts/...).
    Corrected in README.md, CLAUDE.md (one sentence, rationale only — no governance content),
    and CONTRIBUTING.md (one table cell).
  • README tree: resynced with reality (missing skill, ~20 missing scripts/utils
    entries); source-of-truth disclaimer extended to the whole tree.

No tracking issue — this description is the stated scope.
No tests affected (docs-only).

@qodo-code-review

Copy link
Copy Markdown

Code Review by Qodo

🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0)

Grey Divider

Great, no issues found!

Qodo reviewed your code and found no material issues that require review

Grey Divider

Tip of the day
💡 Did you know, you can turn on the rule miner and Qodo learns your standards from review history

More tips ↗ | Customize Qodo ↗ | Qodo docs ↗

Grey Divider

Qodo Logo

@qodo-code-review

Copy link
Copy Markdown

PR Summary by Qodo

Correct marketplace installation and shared script documentation

📝 Documentation 🕐 10-20 Minutes

Grey Divider

AI Description

• Correct marketplace installation commands and explain plugin caching and first-run dependency
 setup.
• Replace outdated shared-script symlink claims with the relative paths skills use.
• Refresh the README directory tree to reflect current skills and scripts.
Diagram

graph TD
  M["Marketplace"] --> C[("Plugin cache")] --> S["Skills"] --> R["Root scripts"]
  S --> D["Python dependencies"]
Loading
High-Level Assessment

The focused documentation correction fits the existing plugin layout. Changing installation or restoring shared-script symlinks would introduce behavior changes to address inaccurate instructions.

Files changed (3) +40 / -15

Documentation (3) +40 / -15
CLAUDE.mdCorrect the shared-script architecture description +1/-1

Correct the shared-script architecture description

• Replaces the obsolete skill symlink-chain description with the plugin-root scripts directory and the relative paths used to reach it.

CLAUDE.md

CONTRIBUTING.mdCorrect the contributor project layout +1/-1

Correct the contributor project layout

• Describes shared scripts as living at the plugin root rather than under a skill-level symlink.

CONTRIBUTING.md

README.mdFix installation guidance and refresh the directory tree +38/-13

Fix installation guidance and refresh the directory tree

• Uses the Claude CLI command for marketplace installation, retains the in-app command as an alternative, and explains plugin caching and first-run dependency setup. Removes stale symlink and manual marketplace setup claims, then updates the illustrated skills and scripts layout.

README.md

@fullsend-ai-review

fullsend-ai-review Bot commented Oct 28, 2026 •

Copy link
Copy Markdown

🤖 Finished Review · ✅ Success · Started 5:07 PM UTC · Completed 5:23 PM UTC

Commit: 8362729 · View workflow run →

Runtime: pi · Model: sonnet → claude-sonnet-5-5 · Effort: high · Cost: $1.58

@fullsend-ai-review fullsend-ai-review Bot added the risk/moderate PR risk: moderate label Oct 28, 2026
@fullsend-ai-review

fullsend-ai-review Bot commented Oct 28, 2026 •

Copy link
Copy Markdown

<!-- fullsend:risk-assessment -->
Risk Assessment: moderate (2/5)

Details

Small documentation-only update with minimal blast radius, assigned moderate risk due to modifying protected path CLAUDE.md alongside recent regression history and historical change coupling on README.md.

Previous run

<!-- fullsend:risk-assessment -->
Risk Assessment: moderate (2/5)

Details

Small documentation-only update with minimal blast radius, assigned moderate risk due to modifying protected path CLAUDE.md alongside recent regression history and historical change coupling on README.md.

Previous run (2)

<!-- fullsend:risk-assessment -->
Risk Assessment: moderate (2/5)

Details

Small documentation-only update with minimal blast radius, assigned moderate risk due to modifying protected path CLAUDE.md alongside recent regression history and historical change coupling on README.md.

@fullsend-ai-review

fullsend-ai-review Bot commented Oct 28, 2026 •

Copy link
Copy Markdown

Review

Findings

High

  • [protected-path] CLAUDE.md — This PR modifies a protected governance file (CLAUDE.md), and the PR has no linked issue (the body states "No tracking issue"), so there is no issue-level justification for changing it. The edit itself is a one-sentence rationale-only change, but human approval is always required for protected-path changes.

Medium

  • [logic-error] README.md:53 — The new text says "The test-plan skills install their Python dependencies on first run." with no exception, but /test-plan-ui-verify does not install its own dependencies: skills/test-plan-ui-verify/README.md tells users to run pip install playwright && playwright install chromium, the ui-verify scripts print an error and stop when Playwright is missing, and the root pyproject.toml has no playwright dependency. The PR body states the exception "(except /test-plan-ui-verify)", but it did not make it into README.md, so marketplace users following the install instructions cannot run UI verification without extra setup.
    Remediation: Add an exception for /test-plan-ui-verify to the first-run dependency sentence and point to the prerequisites in skills/test-plan-ui-verify/README.md.

Low

  • [missing-authorization] PR-level — The PR makes non-trivial documentation changes (about 55 lines across README.md, CLAUDE.md and CONTRIBUTING.md) with no linked tracking issue; the PR description is the only stated scope.
  • [doc-style] README.md:392 — In the skills directory tree, the inline comment on the test-plan-ui-verify scripts/ entry starts one column to the right of the other skill comments.
    Remediation: Remove one space before # on that line so it aligns with the other comments.
  • [doc-style] README.md:435 — Inline comments in the scripts directory tree are not aligned: several newly added entries (get_filtered_tcs.py, get_framework.py, load_calibration.py, load_test_context.py, parse_skill_args.py) put the comment one column left of most entries.
    Remediation: Align the inline comments in the scripts tree to a single column.

Next steps:

  • /fs-fix — agent addresses review findings automatically
  • /fs-fix <your instruction> — agent fixes with your specific guidance
  • Push commits directly — review re-runs automatically on push
  • /fs-fix-stop — disable automatic fix runs for this PR
Previous run

<!-- fullsend:review-findings-v2:eyJ2ZXJzaW9uIjoyLCJhY3Rpb24iOiJyZXF1ZXN0LWNoYW5nZXMiLCJmaW5kaW5ncyI6W3sic2V2ZXJpdHkiOiJtZWRpdW0iLCJjYXRlZ29yeSI6ImxvZ2ljLWVycm9yIiwiZmlsZSI6IlJFQURNRS5tZCIsImlkIjoiZl84NWY3MzBjOTYyZTQyYjAwIiwibGluZSI6NTMsImFjdGlvbmFibGUiOnRydWV9LHsic2V2ZXJpdHkiOiJsb3ciLCJjYXRlZ29yeSI6Im1pc3NpbmctYXV0aG9yaXphdGlvbiIsImZpbGUiOm51bGwsImlkIjoiZl80MmYxMmViMTQ4YzI1N2FmIiwiYWN0aW9uYWJsZSI6ZmFsc2V9LHsic2V2ZXJpdHkiOiJsb3ciLCJjYXRlZ29yeSI6ImRvYy1zdHlsZSIsImZpbGUiOiJSRUFETUUubWQiLCJpZCI6ImZfMjljYzgzN2ZlOGQxMGQyNCIsImxpbmUiOjQzMywiYWN0aW9uYWJsZSI6ZmFsc2V9LHsic2V2ZXJpdHkiOiJsb3ciLCJjYXRlZ29yeSI6ImRvYy1zdHlsZSIsImZpbGUiOiJSRUFETUUubWQiLCJpZCI6ImZfYTdmNzM5ZTYyZThlOTJiNCIsImxpbmUiOjM5MSwiYWN0aW9uYWJsZSI6ZmFsc2V9XSwiZGlzcG9zaXRpb25zIjpbeyJpZCI6ImZfNDJmMTJlYjE0OGMyNTdhZiIsInN0YXR1cyI6Im9wZW4ifV19 -->

Review

Findings

High

  • [protected-path] CLAUDE.md:24 — This PR modifies a protected governance file (CLAUDE.md) and has no linked issue. The description explains the rationale and states "No tracking issue — this description is the stated scope", but protected-path changes without a linked issue lack formal authorization. Human approval is always required for protected-path changes.
    Remediation: Link a tracking issue that authorizes the CLAUDE.md edit, or have a human maintainer explicitly approve the change.

Medium

  • [logic-error] README.md:53 — The line "The test-plan skills install their Python dependencies on first run." applies to every skill, including /test-plan-ui-verify, which does not install its own dependencies. Its README tells users to install Playwright, Chromium and PyYAML manually, and its scripts exit with a pip install ... error when they are missing. The PR body itself names this skill as an exception, but the README text does not.
    Remediation: Qualify line 53, e.g. "(except /test-plan-ui-verify, which needs Playwright, Chromium and PyYAML installed manually; see skills/test-plan-ui-verify/README.md)".

Low

  • [missing-authorization] PR-level — The PR has non-trivial documentation changes across CLAUDE.md, CONTRIBUTING.md and README.md but no linked issue. All hunks are docs-only and stay within the scope the description states.
  • [doc-style] README.md:433 — Five entries added to the scripts/ tree (get_filtered_tcs.py, get_framework.py, load_calibration.py, load_test_context.py, parse_skill_args.py) put the # comment delimiter at column 28, not the column 29 most neighbouring entries use. Cosmetic.
    Remediation: Add one space before # in these entries.
  • [doc-style] README.md:391 — The scripts/ comment under test-plan-ui-verify has 13 spaces before # (column 30) while neighbouring entries align at column 29. Cosmetic.
    Remediation: Use 12 spaces before #.

Next steps:

  • /fs-fix — agent addresses review findings automatically
  • /fs-fix <your instruction> — agent fixes with your specific guidance
  • Push commits directly — review re-runs automatically on push
  • /fs-fix-stop — disable automatic fix runs for this PR
Previous run (2)

<!-- fullsend:review-findings-v2:eyJ2ZXJzaW9uIjoyLCJhY3Rpb24iOiJyZXF1ZXN0LWNoYW5nZXMiLCJmaW5kaW5ncyI6W3sic2V2ZXJpdHkiOiJsb3ciLCJjYXRlZ29yeSI6Im1pc3NpbmctYXV0aG9yaXphdGlvbiIsImZpbGUiOiJSRUFETUUubWQiLCJpZCI6ImZfNDJmMTJlYjE0OGMyNTdhZiIsImFjdGlvbmFibGUiOmZhbHNlfV19 -->

Review

Findings

High

  • [protected-path] CLAUDE.md:24 — This PR modifies CLAUDE.md, which is on the protected-paths list (governance/infrastructure file). The PR has no linked issue and an empty description, so nothing explains why the file is being changed. Human approval is always required for protected-path changes.
    Remediation: Link a tracking issue and describe the rationale in the PR body (the change replaces the stale _common/scripts symlink-chain claim with the relative-path layout). A human maintainer must approve the CLAUDE.md change.

Low

  • [missing-authorization] README.md — The PR title, body (empty) and single commit reference no linked issue. AGENTS.md ("Commits and PRs") and CONTRIBUTING.md ask commit subjects to reference the issue (Closes #NN). The README tree refresh (new skills and roughly 20 new scripts/ and scripts/utils/ entries) also goes beyond the title's "marketplace install instructions and stale symlink claims", so with no issue there is no stated scope to check it against.
    Remediation: Link a tracking issue in the PR description and commit (Closes #NN). If none exists, describe the intended scope in the PR body, including the README tree refresh.

Labels: Documentation-only change to README, CLAUDE.md and CONTRIBUTING.md.


Next steps:

  • /fs-fix — agent addresses review findings automatically
  • /fs-fix <your instruction> — agent fixes with your specific guidance
  • Push commits directly — review re-runs automatically on push
  • /fs-fix-stop — disable automatic fix runs for this PR

fullsend-ai-review[bot]

This comment was marked as outdated.

@fullsend-ai-review fullsend-ai-review Bot added the kind/documentation Improvements or additions to documentation label Oct 28, 2026
@fullsend-ai-review

fullsend-ai-review Bot commented Oct 30, 2026 •

Copy link
Copy Markdown

🤖 Finished Review · ✅ Success · Started 9:26 AM UTC · Completed 9:33 AM UTC

Commit: 38aa230 · View workflow run →

Runtime: pi · Model: sonnet → claude-sonnet-5-5 · Effort: high · Cost: $1.23

fullsend-ai-review[bot]

This comment was marked as outdated.

@fullsend-ai-review

fullsend-ai-review Bot commented Oct 30, 2026 •

Copy link
Copy Markdown

🤖 Finished Review · ✅ Success · Started 11:09 AM UTC · Completed 11:17 AM UTC

Commit: 5d2c0e4 · View workflow run →

Runtime: pi · Model: sonnet → claude-sonnet-5-5 · Effort: high · Cost: $1.36

@fullsend-ai-review fullsend-ai-review Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

See the review comment for full details.

Comment thread README.md
uv sync --extra dev
```
The marketplace install copies the plugin into Claude Code's plugin cache and makes the skills available.
The test-plan skills install their Python dependencies on first run.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[medium] logic-error

The new text says "The test-plan skills install their Python dependencies on first run." with no exception, but /test-plan-ui-verify does not install its own dependencies: skills/test-plan-ui-verify/README.md tells users to run pip install playwright && playwright install chromium, the ui-verify scripts print an error and stop when Playwright is missing, and the root pyproject.toml has no playwright dependency. The PR body states the exception "(except /test-plan-ui-verify)", but it did not make it into README.md, so marketplace users following the install instructions cannot run UI verification without extra setup.

Suggested fix: Add an exception for /test-plan-ui-verify to the first-run dependency sentence and point to the prerequisites in skills/test-plan-ui-verify/README.md.

Comment thread README.md
│ ├── README.md
│ └── SKILL.md
│ ├── SKILL.md
│ └── scripts/ # Playwright-based browser automation (own scripts)

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[low] doc-style

In the skills directory tree, the inline comment on the test-plan-ui-verify scripts/ entry starts one column to the right of the other skill comments (e.g. SKILL.md # Main orchestration skill).

Suggested fix: Remove one space before # on that line so it aligns with the other comments.

Comment thread README.md
├── discover_feature_dir.py # Read and validate the saved feature output-dir marker
├── ensure_feature_test_dir.py # Find or create a feature package under the component test directory
├── get_component_test_dir.py # Map TestPlan.md components to a target-repository test directory
├── get_filtered_tcs.py # Filter test cases for implementation

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[low] doc-style

Inline comments in the scripts directory tree are not aligned: several newly added entries (get_filtered_tcs.py, get_framework.py, load_calibration.py, load_test_context.py, parse_skill_args.py) put the comment one column left of most entries.

Suggested fix: Align the inline comments in the scripts tree to a single column.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

kind/documentation Improvements or additions to documentation risk/moderate PR risk: moderate

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant