skills.rest
Lingtai-AI
Lingtai-AIOFFICIAL
Explore all skills by this author →
GitHub

dev-guide-pr-review-deliverables

Prepares pull requests for review with readiness gates, independent review passes, and self-contained HTML explainers.

692|60|Updated Mar 15, 2026
Search Tags:#deliverables#Git Workflow#gitHub#html report#review gates#Code review#Pull request
One-click install
npx skills add https://github.com/Lingtai-AI/lingtai --skill dev-guide-pr-review-deliverables
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dev-guide-pr-review-deliverables
Source: https://github.com/Lingtai-AI/lingtai/tree/main/tui/internal/preset/skills/lingtai-dev-guide/reference/pr-review-deliverables
Command: npx skills add https://github.com/Lingtai-AI/lingtai --skill dev-guide-pr-review-deliverables

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Getting a pull request truly review-ready involves more than pushing code: the diff must be clean and validated, an independent reviewer must check it, and the human maintainer needs a clear written explanation. This Skill consolidates those PR readiness gates, review-pass procedures, and deliverable conventions into one operational reference.

Core Features & Use Cases

  • PR Readiness Gate: A checklist covering clean diffs (git diff --check), targeted tests, anatomy/skill-catalog updates in the same commit, and secret redaction.
  • Independent Review Passes: Procedures for read-only multi-model or daemon reviews (Claude Code, Codex) treated as gates, with guidance on classifying findings without scope creep.
  • HTML Explainer Conventions: Rules for writing self-contained, local-only HTML explainers with required sections (TL;DR, baseline, validation, risks, source index) and naming/timing conventions.
  • Authorization Boundaries: Explicit rules that opening, editing, or merging PRs requires per-action maintainer authorization, plus gh pr edit troubleshooting notes.
  • Use Case: Before asking a maintainer to merge a fix, run the readiness gate, obtain a read-only daemon review of the diff, write pr123-fix-login-explainer.html to an ignored artifacts path, and hand the maintainer the file path with a short pointer message.

Quick Start

Ask the agent to prepare the current branch's pull request for review by running the readiness gate, an independent read-only review pass, and writing a self-contained HTML explainer.

Frequently Asked Questions about dev-guide-pr-review-deliverables

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

FAQPage Schema
How do I prepare a pull request for review before merging?▼

Run a readiness gate: check the diff with git diff --check, run targeted tests for the changed area, confirm no secrets or private paths are present, and write a self-contained HTML explainer. Then obtain at least one independent read-only review pass before asking for a merge.

How to get an independent code review of a diff with AI tools?▼

Generate a diff prompt and have a read-only daemon such as Claude Code or Codex, or a second model, review correctness, scope, and regressions. Save the review as an auditable artifact, then classify each finding yourself against the actual diff rather than trusting the summary.

What should a pull request explainer document contain?▼

A self-contained single HTML file with inline CSS and no remote assets, containing sections in order: TL;DR conclusion, baseline, what was done with diff snippets, validation commands and results, risks and decisions, next steps, and a source index. Routine explainers stay local and are not committed.

Why does gh pr edit show GraphQL deprecation warnings?▼

Some versions of the GitHub CLI emit GraphQL deprecation warnings when running gh pr edit; these are warnings, not failures. If gh pr edit --body-file is noisy, re-run it or set the body through the web UI instead.

Can an AI agent open or merge pull requests on its own?▼

No. Opening, editing, or merging PRs, pushing commits, and filing or closing issues are external side effects that require an explicit maintainer authorization for that specific action. Generating diffs, running read-only reviews, and writing local explainers are always permitted.

Related Skills

Explore More Software Engineering Skills→
GuicedEEGuicedEE
5

finishing-a-development-branch

Verify tests, clean diffs, and prepare a development branch for review.

Official
Intermediate
NVIDIANVIDIA
3.4k

release-cherry-pick

Cherry-pick labeled merged pull requests into release branches via GitHub CLI.

Official
Advanced
webmaxruwebmaxru
49

test-discipline

Update assertions in the same commit when public interfaces change to keep CI reliable.

Community
Intermediate
BluMintIncBluMintInc
2

automated-review-addressing

Automate pull request review feedback by updating the PR head branch.

Official
Advanced