How this skill is triggered — by the user, by Claude, or both
Slash command
/homepage-plugin:hp-fixThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Fixes issues identified by the `hp-review` skill or verification failures from `hp-verify`. All fixes are direct (no TDD classification) since homepage sections are primarily presentational.
Fixes issues identified by the hp-review skill or verification failures from hp-verify. All fixes are direct (no TDD classification) since homepage sections are primarily presentational.
Read .claude/homepage-plugin.json. If not found, exit with instruction to run /homepage-plugin:hp-init.
Read defaultLocale — all user-facing output in this language.
Required files:
docs/pages/{page-name}/page-plan.json — page plandocs/pages/{page-name}/.progress/{page-name}.json — progress filedocs/pages/{page-name}/.implementation/homepage/review-report.json — review report (required for review-failed, reviewed, fixing statuses)Check progress status:
review-failed, reviewed (with warnings), fixing, verified, verify-failed, escalatedplanned, generated, donegenerated: instruct user to run /homepage-plugin:hp-verify or /homepage-plugin:hp-review firstverified or verify-failed without review-report.json: run verification-based fixes using hp-verify output (tsc/eslint/build errors) instead of review issuesescalated: user has manually intervened and wants to re-run fixesRead fix history from docs/pages/{page-name}/.implementation/homepage/fix-report.json (if exists):
Same lock protocol as hp-gen Step 3 (JSON format with lockedBy, lockedAt, pageName; 30-min stale threshold).
Lock file path: docs/pages/{page-name}/.implementation/homepage/.lock
lockedBy: "hp-fix"Launch review-fixer agent with:
pageName — page identifierplanFile — path to page-plan.jsonprojectRoot — project rootreviewReportFile — path to review-report.jsonconfig — homepage-plugin configurationThe agent will:
Save agent output to docs/pages/{page-name}/.implementation/homepage/fix-report.json:
{
"timestamp": "2026-03-23T...",
"round": 1,
"issuesReceived": 5,
"issuesFixed": 4,
"issuesSkipped": 1,
"escalated": [],
"verification": {
"tsc": "pass",
"eslint": "pass",
"build": "pass"
}
}
Update docs/pages/{page-name}/.progress/{page-name}.json:
fixing (needs re-review)fixing (needs re-review)escalated (manual intervention)Release docs/pages/{page-name}/.implementation/homepage/.lock.
Show fix summary:
Fix Results (Round 1):
Issues received: 5
Issues fixed: 4
Issues skipped: 1 (already resolved)
Escalated: 0
Verification: tsc ✓ | ESLint ✓ | Build ✓
Next step: Run /homepage-plugin:hp-review to re-review.
If escalated:
Fix Results (Round 3):
Escalated issues: 2
1. [accessibility] Complex focus management in ContactForm — needs manual review
2. [seo] Dynamic OG image generation — requires build pipeline change
These issues require manual intervention.
After resolving, re-enter pipeline via /homepage-plugin:hp-review.
After 3 fix rounds with remaining issues:
Warning: 3 fix rounds completed with unresolved issues.
Possible actions:
1. Review and manually fix remaining issues
2. Re-plan the page: /homepage-plugin:hp-plan {page-name}
3. Accept current state and mark as done
Read defaultLocale from .claude/homepage-plugin.json for all user-facing output.
npx claudepluginhub ohmyhotelco/hare-cc-plugins --plugin homepage-pluginFixes assets that fail review by performing root cause analysis, generating a fix brief, reproducing in isolated context, and re-verifying. Capped at 3 attempts per asset.