review

Diff sprint artefacts against the integration baseline and consolidate review findings.

4|1|Updated Apr 11, 2026

Search Tags:#automation #security #requirements #review #diff #code-review #sprint

Ready to run

npx skills add https://github.com/nicolasguelfi/gensem --skill review-nicolasguelfi

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: review
Source: https://github.com/nicolasguelfi/gensem/tree/main/gse-one/plugin/skills/review
Command: npx skills add https://github.com/nicolasguelfi/gensem --skill review-nicolasguelfi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Review all sprint artefacts by diffing the current sprint against the integration baseline, surfacing gaps, inconsistencies, and actionable findings.

Core Features & Use Cases

Diff-based review across sprint artefacts (requirements, design, test strategy, backlog) to surface changes and potential regressions.
Parallel sub-agent analysis (code quality, security, requirements, design, tests) with a consolidated review document.
Automated health and status updates, including a final review report stored at docs/sprints/sprint-{NN}/review.md and optional FIX workflow.

Quick Start

Trigger a sprint review by issuing /gse:review in your project workspace.

Frequently Asked Questions about review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate sprint review across multiple code quality and security dimensions?▼

Automate sprint review by diffing the current sprint against the integration baseline and running parallel sub-agents for code quality, security, requirements, design, and tests. This surfaces gaps and consolidates findings into a single review document.

What is a diff-based sprint review and how does it surface regressions?▼

A diff-based sprint review compares current sprint artefacts against the integration baseline to identify changes and potential regressions. It analyzes requirements, design, and test strategy to surface inconsistencies and actionable findings across the project.

How do I generate a consolidated sprint review report categorized by severity?▼

Generate a consolidated review report by running parallel sub-agents that merge analysis results into a markdown file. Findings are categorized by severity, linked to requirements where possible, and stored at docs/sprints/sprint-{NN}/review.md.

Can I trigger automated health and status updates after a sprint code review?▼

Yes, sprint code review triggers automated health and status updates by categorizing findings and optionally initiating a FIX workflow. These updates are integrated directly into the project health metrics after the review is completed.

Does this sprint review tool require specific dependencies to run parallel analysis?▼

No, this sprint review tool requires no external dependencies to run parallel analysis. It operates natively within the project workspace to execute sub-agents for code quality, security, requirements, design, and tests.

When should I use a devil's advocate approach for sprint artefact review?▼

Use a devil's advocate approach for sprint artefact review when you need to critically evaluate requirements, design, and code changes against the integration baseline. It is ideal for surfacing hidden gaps and inconsistencies before final integration.