review

Review GitHub issues and verify implementations against acceptance criteria.

Updated Jul 6, 2026
One-click install
npx skills add https://github.com/duongtdn/devloop --skill review-duongtdn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/duongtdn/devloop/tree/main/skills/review
Command: npx skills add https://github.com/duongtdn/devloop --skill review-duongtdn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill bridges the gap between autonomous AI execution and human oversight, ensuring that shipped software is verified, understood, and accepted by the product owner rather than just blindly merged.

Core Features & Use Cases

  • Task Acceptance: Review individual GitHub issues, verify implementation against acceptance criteria, and manage PR merges.
  • Sprint Retrospectives: Conduct end-of-sprint ceremonies, including retrospective writing, release tagging, and milestone closure.
  • Independent Verification: Perform real-world system demos to catch green-but-unreachable code and verify behavior at the entry point.

Quick Start

Use the review skill to inspect the work completed for issue number 42 and proceed with the acceptance process.

Frequently Asked Questions about review

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

FAQPage Schema
How do I verify autonomous software development tasks before merging code?

To verify autonomous software development tasks, you need human-in-the-loop review to reconcile AI-generated logs with real-world system behavior. This ensures code reachability and product acceptance through conversational review before merging.

How do I perform a sprint retrospective and close GitHub milestones?

Performing a sprint retrospective involves conducting end-of-sprint ceremonies to review outcomes, write retrospectives, tag releases, and close GitHub milestones. This process validates the overall sprint progress and artifacts.

What is the best way to catch green-but-unreachable code in a local development environment?

The best way to catch green-but-unreachable code is through independent verification using real-world system demos. This validates actual behavior at the entry point rather than relying solely on passing test logs.

Can I use this human-in-the-loop review skill to accept individual GitHub issues?

Yes, you can use this human-in-the-loop review skill to accept individual GitHub issues. It facilitates reviewing the implementation against acceptance criteria and managing pull request merges.

Do I need GitHub issue tracking integration for task acceptance?

Yes, you need GitHub issue tracking integration and local development environment state for task acceptance. These dependencies are required to validate code reachability and verify product behavior accurately.