report-check
暂无简介
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-14
- Stars
- ★ 1.6k
- Forks
- 491
02 资源文件 1
- 参考文档TEST-PLAN.md1.4 KB
03 SKILL.md 正文
Gather Context
!`git rev-parse --is-inside-work-tree 2>/dev/null || echo "NO_GIT"`
!`git branch --show-current 2>/dev/null || echo "NO_GIT"`
Report Quality Check
Analyze a review report for quality issues -- noise, false positives, overkill suggestions, and findings that exist to appear thorough rather than to help the developer.
Announce: "Using the report-check skill to audit report quality."
Step 0 -- Validate Input
If $ARGUMENTS is empty, print:
Usage:
/report-check <path-to-review-report.md>Analyzes a review report for quality issues -- noise, false positives, overkill suggestions.
Stop here.
If $ARGUMENTS contains a file path:
- Read the file using the Read tool.
- If the file does not exist or is not readable, print:
Report file not found:
{path}Stop here.
Step 1 -- Read Report
- Read the full report file.
- Extract the branch name from the
## Review Contextsection if present (look for aBranch:line). - Note the report structure: findings grouped by severity, verdict, filtered findings section.
Step 2 -- Reconstruct Diff (optional)
If git is available AND a branch name was extracted from the report:
-
Determine the base branch:
!`git rev-parse --verify main 2>/dev/null || echo "NO_MAIN"`Use
mainif it exists, otherwisemaster. -
Get the diff:
!`git diff {base}...{branch} 2>/dev/null || echo "NO_DIFF"` -
If the diff is non-empty, it will be passed to the agent for cross-referencing.
Print status:
- With diff:
Analyzing report with diff cross-reference... - Without diff:
Analyzing report (no diff available for cross-reference)...
If git is unavailable or no branch info exists, proceed without diff. The agent works report-only -- Phase 2 accuracy checks will be limited.
Step 3 -- Dispatch Agent
Spawn the quiver:report-checker agent with a self-contained prompt containing:
-
The full report content, clearly delimited:
<report> {full report markdown} </report> -
The diff (if available), clearly delimited:
<diff> {full diff output} </diff>If no diff is available, include:
<diff> No diff available for cross-referencing. </diff> -
Instruction: "Audit this review report for quality. Apply all three phases (substance verification, accuracy check, proportionality audit). Return structured findings using your output format."
Step 4 -- Present Results
If agent returns zero issues:
Report passed quality audit -- no issues found.
If agent returns issues, display the structured findings to the user.
Use AskUserQuestion:
Quality audit found {N} issues in the report. What would you like to do?
Buttons:
Apply fixes to the reportShow details onlySkip -- keep as-is
Handle each option:
<!-- SYNC: The apply-fixes procedure below (REMOVE/DOWNGRADE/REWRITE actions + recalculation steps) is duplicated in skills/review/SKILL.md Step 3.5 "Handle results" block. Keep both in sync. --> Apply fixes:
- For each issue with action REMOVE: delete the finding from the report file.
- For each issue with action DOWNGRADE: change the finding's severity and move it to the correct severity section.
- For each issue with action REWRITE: replace the finding's recommendation text with the corrected version. It changes only the recommendation text, so the finding keeps its
Verification:line. - After applying all fixes, recalculate:
- Findings overview counts in
## Review Context - Disposition counts in
## Review Context, and the**Deferred:**line under the fix order table - Severity section contents (move downgraded findings, remove deleted ones)
- Recommended Fix Order table (remove entries for deleted/downgraded findings)
- Verdict line (recompute based on remaining finding severities)
- Findings overview counts in
- Write the updated report back to the same file path.
- Proceed to Step 5.
Show details:
- Print the full audit output.
- Re-ask via
AskUserQuestion:Apply the suggested fixes? Buttons:
Apply fixes/Skip -- keep as-is
Skip: Stop. Report unchanged.
Step 5 -- Verify (if fixes applied)
- Read the modified report file back using the Read tool.
- Confirm no
{placeholder}text remains in the report. - Print:
Report updated: {N} findings removed, {M} downgraded, {K} rewritten.
04 同仓库更多 Skills
worktable-review-with-annotations
Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.
worktable-find-and-synthesize-context
Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.
worktable-create-or-update-docs
Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.
worktable-create-or-manage-records
Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.
worktable-create-or-manage-interactive-html
Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.
worktable-collaborate-threads
Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.