skills.rest
inkeep
inkeepOFFICIAL
Explore all skills by this author →
Website𝕏@inkeepGitHub

review

Manage the Pull Request review loop by polling feedback, assessing suggestions, and resolving CI/CD checks.

Updated Aug 27, 2026
Search Tags:#code quality#ci/cd#code review#developer workflow#github actions#pr review
One-click install
npx skills add https://github.com/inkeep/team-skills --skill review-inkeep
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/inkeep/team-skills/tree/main/plugins/eng/skills/review
Command: npx skills add https://github.com/inkeep/team-skills --skill review-inkeep

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the entire Pull Request (PR) review process, from gathering feedback to resolving CI/CD issues, ensuring your code gets merged efficiently and with high quality.

Core Features & Use Cases

  • Automated Feedback Loop: Continuously polls for reviewer comments and CI/CD status.
  • Evidence-Based Assessment: Evaluates suggestions with rigorous investigation, not blind acceptance.
  • CI/CD Resolution: Investigates and fixes failing checks, differentiating between PR-caused and pre-existing issues.
  • Use Case: When you submit a PR, this Skill can automatically monitor for comments, help you analyze each suggestion, implement fixes, run tests, and ensure the CI pipeline passes before merging.

Quick Start

Use the review skill to manage the PR review iteration loop for pull request number 123.

Frequently Asked Questions about review

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

FAQPage Schema
How do I automate the PR review loop and resolve reviewer comments?▼

Automating the PR review loop involves polling for reviewer comments, evaluating suggestions with evidence, implementing fixes, and resolving threads to drive CI/CD pipelines to green. This process ensures code gets merged efficiently by continuously monitoring feedback and automatically addressing required changes.

How do I fix failing CI/CD checks caused by a pull request?▼

Fixing failing CI/CD checks requires investigating the pipeline failures and differentiating between PR-caused and pre-existing issues. Once identified, you implement the necessary fixes, run tests locally, and monitor the pipeline until all checks pass green before merging.

What is the best way to address GitHub Actions feedback on a pull request?▼

Addressing GitHub Actions feedback requires an evidence-based assessment of automated comments rather than blind acceptance. You investigate the validity of each suggestion, implement the required code fixes, and verify the pipeline passes before resolving the conversation threads.

Can I use a SPEC.md file to guide code review assessment?▼

Yes, providing a SPEC.md file enables spec-aware assessment during the PR review cycle. The review process uses this specification to rigorously evaluate reviewer feedback and code changes against your defined requirements, ensuring fixes align with the intended project architecture.

How do I resolve GitHub PR review threads automatically?▼

Resolving GitHub PR review threads requires implementing the requested fixes for each comment, running tests to verify the changes, and confirming the CI/CD pipeline reaches green. Once the feedback loop determines all issues are addressed, the conversation threads are resolved.

Related Skills

Explore More Software Engineering Skills→
SimpleEveSimpleEve
30

eo-module-init

Create a validated module spec and initial review baseline.

Community
Intermediate
a29paula29paul
1

land-and-deploy

Merge approved PRs, wait for CI and deployment pipelines, and verify production canary checks.

Community
Advanced
BillChiricoBillChirico
5

github-pr-resolver

Resolve GitHub pull request review threads and failing CI checks with commits.

Community
Advanced
leocostaleocosta
4

respond-to-review

Verify PR review comments against code and complete the post-fix loop.

Community
Advanced