Results for “review-report”

Produces academic papers, literature reviews, grant proposals, and clinical reports with LaTeX formatting and verified citations, using research-lookup and parallel-web skills.

Read, create, and review PDF files with visual rendering checks using Poppler, reportlab, pdfplumber, and pypdf.

Prepare PRINCE2 Closing a Project material: product acceptance, end project report, lessons report, benefits review plan, handover, follow-on actions, and closure recommendation.

Multi-perspective academic paper review with dynamic reviewer personas. Simulates 5 independent reviewers (EIC + 3 peer reviewers + Devil's Advocate) with field-specific expertise. Supports full review, re-review (verification), quick assessment, methodology focus, Socratic guided, and calibration modes. Triggers on: review paper, peer review, manuscript review, referee report, review my paper, critique paper, simulate review, editorial review, calibrate reviewer, reviewer calibration, measure reviewer accuracy.

Generate academic referee reports for economics/finance papers, followed by a 150-word letter to the editor with recommendation (Reject / Major Revision) and Kai Wu signature. Two modes (normal / high-level), configurable number of comments; recommendation choice drives evaluation tone (Reject → negative, Major Revision → neutral). Trigger when user says "referee report" / "write referee report" / "审稿报告" / "写审稿意见" / "generate referee report" / "review this paper".

Walk every branching path and boundary condition in content, report only unhandled edge cases. Orthogonal to adversarial review - method-driven not attitude-driven. Use when you need exhaustive edge-case analysis of code, specs, or diffs.

Revise an academic paper based on internal review comments. Reads review report or annotated manuscript, then applies revisions one by one with user approval. Trigger when user says "self revise" / "paper-selfrevise" / "内部修改" / "根据审稿意见修改".

Walk every branching path and boundary condition in content, report only unhandled edge cases. Orthogonal to adversarial review - method-driven not attitude-driven. Use when you need exhaustive edge-case analysis of code, specs, or diffs.

Walk every branching path and boundary condition in content, report only unhandled edge cases. Orthogonal to adversarial review - method-driven not attitude-driven. Use when you need exhaustive edge-case analysis of code, specs, or diffs.

Use when the superpowers-evaluator returned REWORK on a batch, when fixing rework items from an evaluation report, or when receiving any code review feedback on superpowers output. Requires technical rigor and verification instead of performative agreement or blind implementation.

Generate test report. Use when user says "test report", "results summary", "test status", "show results", "test dashboard", or "how did tests go".

Scans copy for AI-generated writing patterns and outputs a diagnostic report. Diagnosis only by default.

Guides a structured software requirements specification workflow from topic intake through brainstorming, spec writing, planning, review, SRS generation, validation, and improvement reporting.

Write grant reports with progress, financials, and outcomes. TRIGGERS - Use when user needs help with grant-report related tasks.

Generate test report. Use when user says "test report", "results summary", "test status", "show results", "test dashboard", or "how did tests go".

Write grant reports with progress, financials, and outcomes. TRIGGERS - Use when user needs help with grant-report related tasks.

Vulnerability Report

Incident Report (Blameless RCA)

Turn raw revenue data into a weekly or monthly wrap-up that drives action, not another dashboard screenshot. Position vs plan, what moved, the risks worth naming, and the specific next moves. Built for B2B revenue teams, customizable to your data and your cadence. Trigger on "write the revenue report", "how did we do this month", "revenue wrap-up", "are we on plan", "monthly number", or any revenue-recap request.

Finds root cause before applying fixes for errors, crashes, regressions, failing tests, broken behavior, and screenshot-reported defects. Use when users report in any language errors, crashes, broken behavior, regressions, failing tests, screenshot evidence, or something that used to work and now fails. Not for code review or new features.

product-report

Report-only QA testing. Systematically tests a web application and produces a structured report with health score, screenshots, and repro steps — but never fixes anything. Use when asked to "just report bugs", "qa report only", or "test but don't fix". For the full test-fix-verify loop, use /qa instead. Proactively suggest when the user wants a bug report without any code changes. (gstack) Voice triggers (speech-to-text aliases): "bug report", "just check for bugs".

Capture delivery evidence, commands, changed files, blockers, and standards feedback after a work session.

Generate test report. Use when user says "test report", "results summary", "test status", "show results", "test dashboard", or "how did tests go".

Report-only QA testing. (gstack)

Guides a structured requirements pipeline from topic intake through brainstorming, spec and plan writing, user review, SRS generation, validation, and improvement reporting.

Audits a wiki for contradictions, stale content, orphan pages, duplicates, missing sections, broken wikilinks, and AI-tell contamination, producing a lint report for human review.

Apply findings from a document-health-review report by updating, merging, splitting, moving, archiving, deleting, and repairing references for repository documents. Use when a user wants to execute approved document cleanup recommendations.

Use when tasks involve reading, creating, or reviewing PDF files where rendering and layout matter; prefer visual checks by rendering pages (Poppler) and use Python tools such as `reportlab`, `pdfplumber`, and `pypdf` for generation and extraction.

Use when tasks involve reading, creating, or reviewing PDF files where rendering and layout matter; prefer visual checks by rendering pages (Poppler) and use Python tools such as `reportlab`, `pdfplumber`, and `pypdf` for generation and extraction.