review

Generate and evaluate branch diffs to review sprint artefacts across code, security, and requirements.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/tjisousa/gensem --skill review-tjisousa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/tjisousa/gensem/tree/main/gse-one/plugin/skills/review
Command: npx skills add https://github.com/tjisousa/gensem --skill review-tjisousa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Review teams need a structured, automated way to validate sprint artefacts and enforce guardrails across changes, ensuring quality before delivery.

Core Features & Use Cases

  • Parallel multi-perspective review: code quality, security, requirements, design, and test strategies run concurrently to surface issues.
  • Diff-based validation: reviews are performed on the sprint diff against the integration branch to keep scope focused.
  • Devil's advocate pass: automated dissent to challenge findings and improve overall quality.
  • Documentation and health: updates to sprint artefacts and health metrics inform progress and risk.

Quick Start

Invoke /gse:review to start a sprint artefact review with optional devil's advocate.

Frequently Asked Questions about review

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

FAQPage Schema
How do I automate sprint artefact review and enforce quality guardrails before delivery?

Automated sprint artefact review validates changes by generating diffs between feature and integration branches, evaluating code quality, security, and requirements against guardrails. It uses parallel sub-agents to assess multiple perspectives concurrently and aggregates deduplicated findings.

What is a diff-based validation approach for sprint integration branches?

Diff-based validation scopes reviews by comparing the feature branch against the sprint integration branch. This focused approach ensures only relevant changes are evaluated for code quality, security, design coherence, and regression risk before merging.

How do I run parallel code quality and security checks on sprint diffs?

Parallel sub-agents run concurrently to assess code quality, security, requirements completeness, design coherence, and regression risk on sprint diffs. The system orchestrates these multi-perspective reviews simultaneously, then aggregates and deduplicates the results.

Can I use a devil's advocate pass to challenge sprint review findings?

Yes, a devil's advocate pass can be invoked during sprint artefact review to automatically challenge findings. This automated dissent mechanism surfaces counterarguments to improve overall quality and validate initial review results.

Do I need backlog.yaml and plan.yaml to scope sprint reviews?

Yes, backlog.yaml and plan.yaml are required to scope reviews and apply guardrails. The system also relies on test_evidence data to assess regression risk and update sprint documentation and health dashboards.

How does sprint review update documentation and health metrics?

Sprint review updates documentation by writing findings to docs/sprints/review.md and refreshing the health dashboard. These updates inform progress tracking and risk assessment based on the aggregated review results.