Loading...
Loading...
Found 3 Skills
Perform a deep, scoped review of a working tree, staged diff, commit range, branch diff, pull request, focused file set, or pasted code. Use for `/code-review`, PR or diff review, merge-safety assessment, and one bounded post-implementation review. Begin with a read-only orchestration assessment, ground expected behavior in authoritative product or contract evidence, trace propagated risk, persist a canonical lineage-aware report, and never edit code or Git state unless the user separately requests fixes. A post-implementation report is terminal for its automatic review chain.
Create and modify Power BI report files in PBIR/PBIP format using the `powerbi-report-author` and `powerbi-desktop` CLIs. Use when the user wants to: (1) implement an approved report spec or design brief, (2) add or edit pages, visuals, filters, slicers, bookmarks, themes, or formatting, (3) validate PBIR and verify rendering in Power BI Desktop. For open-ended visual design, use `powerbi-report-design` first. For end-to-end requirements and approval workflow, use `powerbi-report-planning` first. Triggers: "edit PBIR", "create Power BI report page", "add visual to PBIP", "format report visual", "validate Power BI report", "reload Desktop screenshot", "implement an approved PBIP report spec", "edit PBIR pages/visuals".
Generate and upsert a Ticket-scoped QA Report (PROGRESS or COMPLETION) for any CawPlan Ticket (anchor) + Version: collect anchor-relative subtree/relation/execution data, apply result rules, render ticket-qa-report.1 template, and persist via existing Portal qa_report POST/PUT. Use when: SQA asks for a test progress or completion QA report for a ticket and version (Story, requirement sub-ticket, or BUGFIX); republish/update an existing linked report; include related/blocking tickets in report scope. NOT for: Version Quality Report or AQA automation rollup; release risk assessment (use A5 separately); importing cases (A1), plan layout (A2), or defect filing (A4). V1 zero-BE: Agent-side upsert; approximate coverage; anchor-relative subtree depth ≤ 3.