skills.rest
minhquan2904
minhquan2904COMMUNITY
Explore all skills by this author →
GitHub

review

Scan openspec/changes and source code to generate delta documentation artifacts.

Updated Mar 27, 2026
Search Tags:#code-review#open-spec#software-engineering#change-management#artifact-generation#delta-spec
One-click install
npx skills add https://github.com/minhquan2904/vibe-check-scam --skill review-minhquan2904
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/minhquan2904/vibe-check-scam/tree/main/.agent/skills/review
Command: npx skills add https://github.com/minhquan2904/vibe-check-scam --skill review-minhquan2904

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates post-implementation reviews by scanning change context and implemented code to produce structured artifacts that capture discoveries, new APIs, and delta behavior.

Core Features & Use Cases

  • Detects change scope from openspec/changes and reads metadata to determine required artifacts.
  • Generates tracking artifacts: todo-uncover.md, new-apis.md, delta-spec.md; for change-requests also generates regression-check.md and migration-note.md.
  • Analyzes implemented source code to surface TODOs, API additions, and behavioral deltas for traceability.

Quick Start

Run the review workflow on a completed change in openspec/changes to generate the tracking artifacts.

Frequently Asked Questions about review

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

FAQPage Schema
How do I automate post-implementation code review for behavioral deltas and new APIs?▼

Automate post-implementation code review by scanning the openspec/changes directory and implemented sources to generate structured artifacts that track new APIs, behavioral deltas, and TODOs. This workflow reads metadata.yaml to determine the required output files for traceability.

What tracking artifacts do I need for change-management and delta-spec generation?▼

Change-management delta-spec generation produces todo-uncover.md, new-apis.md, and delta-spec.md. For change-request variants detected from metadata.yaml, it also generates regression-check.md and migration-note.md to document test coverage and migration paths.

How does scanning openspec/changes identify TODOs and API additions in my codebase?▼

Scanning openspec/changes analyzes implemented source code to surface uncovered TODOs and API additions. It detects the variant type from metadata.yaml and maps the behavioral deltas into structured tracking artifacts for full codebase traceability.

Can I generate regression-check and migration-note files for change-request variants only?▼

Regression-check.md and migration-note.md files are generated specifically for change-request variants. The workflow detects the variant type from metadata.yaml and conditionally produces these additional artifacts alongside the standard delta documentation.

What is the best way to document test coverage and behavioral deltas after a code change?▼

Document test coverage and behavioral deltas by running a review workflow that scans completed changes in openspec/changes. It produces a traceable summary and structured delta documentation, capturing API additions and behavioral shifts across the codebase.

Related Skills

Explore More Software Engineering Skills→
ybenitezfybenitezf

openspec-archive-change

Archive completed OpenSpec changes to a dated directory while preserving .openspec.yaml.

Community
Advanced
zaziedlmzaziedlm

test-coverage-improver

Run make coverage, analyze reports, and propose high-impact tests for approval.

Community
Intermediate
hmj1026hmj1026

openspec-verify-change

Validate code changes against OpenSpec delta specs and tasks.

Community
Intermediate
breuerfelixbreuerfelix
5

openspec-archive-change

Archive completed OpenSpec changes after validation and optional delta-spec sync.

Community
Advanced