test(axis): full coverage for under-tested skill rules across all domains (AX-107)#85
Conversation
|
Warning Review limit reached
Next review available in: 59 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: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (2)
📒 Files selected for processing (58)
✨ Finishing Touches🧪 Generate unit tests (beta)
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 |
…ime (keep anti-workaround)
…'t hand over netlify api restore)
|
Codex review: I audited this against AX-107 and the branch diff. I did not find blocking issues. Generated Codex/Cursor mirrors are in sync, and |
|
Codex review update: I re-audited the new PR head ( |
Summary
Full coverage pass (AX-107) — adds a scenario for every under-tested skill rule the audit's §D surfaced (rules already documented in the skills but previously untested). Scenarios-only; each check is grounded in existing skill text so the with-skill variant scores goal ≥95. (Supersedes the initial four-scenario tranche.)
What changed
pathdisables the default route / 60 s sync ceiling / cron-is-UTC, MCP GET→405 (SSE trap) + 406 Accept-header diagnosis, deploy failed-deploy≠downtime +netlify logssource flags, identity role-change-needs-token-refresh + server-side role gating, caching same-URL-identical-Netlify-Vary+ context-scoped invalidation, edge--geomock +onErrorredirect form, agent-runner--model/errorterminal state / link-prereq, and more.netlify-deploy/SKILL.mdedit — the roll-back guidance backing thedeploy-failure-not-downtimescenario — is the single non-scenario change (QA-noted as not harmful).Closes AX-107.