Land agenza-frontend-feature skill updates missed by the #69 PR split - #77
Conversation
These 3 files (agent-skills/agenza-frontend-feature/SKILL.md and its two synced copies under .claude/skills/ and .agents/skills/) live at the repo root, outside apps/admin-frontend/ — every diff I computed while splitting #69 into #70/#71/#75/#76 was scoped to apps/admin-frontend (and backend/ for #70), so these files' accumulated updates from this session (Catalog Result migration, Auth Result migration, and finally the Tags-removal doc pass replacing TagsPage/TagForm with Categories as the reference implementation) never made it into any of the split PRs, even though the actual code changes they describe are all correctly merged. Content taken directly from the original branch's final commit (4911abb), already reviewed and governance-checked at the time. Verified again here against the current merged main: sync_agent_skills.py --check, check_agent_governance.py, and architecture_guard.py all pass, and the file paths the skill references (CategoriesListPage.tsx, CategoryForm.tsx, categoryMapper.ts, AdminLayout.tsx) all exist in the current tree. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
|
Warning Review limit reached
Next review available in: 53 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (3)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
1 participant
Summary
While verifying #71's changes were fully applied, found that
agent-skills/agenza-frontend-feature/SKILL.mdand its two synced copies (.claude/skills/...,.agents/skills/...) still describeTagsPage/TagFormas the reference implementation and list Tags in the catalog layout — even though #75/#76 already removed Tags from the frontend and made Categories the reference.Root cause: these 3 files live at the repo root, outside
apps/admin-frontend/. Every diff I computed while splitting #69 into #70/#71/#75/#76 was scoped toapps/admin-frontend(andbackend/for #70), so these files' accumulated doc updates from that work — Catalog Result migration, Auth Result migration, and the final Tags-removal pass — never made it into any of the split PRs, even though the actual code changes they describe are all correctly merged. Pure oversight in how I scoped the split, not a disagreement about content.Content taken directly from the original branch's final commit, already reviewed and governance-checked at the time it was written.
Test plan
python scripts/sync_agent_skills.py --check— all 3 copies in syncpython scripts/check_agent_governance.py— passespython scripts/architecture_guard.py— passesCategoriesListPage.tsx,CategoryForm.tsx,categoryMapper.ts,AdminLayout.tsx) — all exist🤖 Generated with Claude Code