skills.rest
tomoasleep
tomoasleepCOMMUNITY
Explore all skills by this author →
𝕏@nemunemu3desuGitHub

self-review

Inspect diffs, base branches, and review threads to validate PR quality standards.

2|Updated Nov 27, 2017
Search Tags:#github#review#code-quality#lint#pull-request#tests#diff-check
One-click install
npx skills add https://github.com/tomoasleep/dotfiles --skill self-review-tomoasleep
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: self-review
Source: https://github.com/tomoasleep/dotfiles/tree/main/config/.claude/skills/self-review
Command: npx skills add https://github.com/tomoasleep/dotfiles --skill self-review-tomoasleep

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill validates that code changes meet defined project quality standards and comply with any given code review comments, without applying modifications to the codebase.

Core Features & Use Cases

  • Validate diffs against established quality gates (lint, tests) and check for unresolved review comments.
  • Report non-conformances and propose actionable follow-up tasks for the author or reviewer.
  • Integrate with GitHub PR workflows to determine merge readiness based on review status.

Quick Start

Run the self-review process on the current pull request by inspecting open diffs, base branch, and outstanding review threads. If issues are found, list them and propose tasks to resolve them without altering code.

Frequently Asked Questions about self-review

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

FAQPage Schema
How do I check if my pull request passes lint and tests before merging?▼

To check if your pull request passes lint and tests, inspect the open diffs and run tooling checks against the base branch. This process validates code changes meet defined project quality gates without modifying the codebase.

How do I verify unresolved GitHub review comments are addressed in my code changes?▼

Verifying unresolved GitHub review comments involves inspecting outstanding review threads alongside the current diff. The process determines merge readiness and outputs actionable follow-up tasks to resolve non-conformances without altering code.

What is the best way to automate code quality checks for a pull request diff?▼

Automating code quality checks for a pull request diff requires inspecting the changes against the base branch and running lint and test validations. This identifies non-conformances and proposes actionable tasks for the author or reviewer to resolve.

Does this code review process apply modifications to my codebase automatically?▼

No, this code review process does not apply modifications to your codebase. It strictly validates diffs against quality standards and review comments, outputting actionable tasks for resolution while leaving the original code untouched.

How do I determine merge readiness based on GitHub PR review status and diff checks?▼

Determining merge readiness involves integrating with GitHub PR workflows to inspect open diffs, base branches, and outstanding review threads. Performing diff verification and tooling checks outputs actionable tasks to resolve remaining issues.

Related Skills

Explore More Software Engineering Skills→
DavidLiuXhDavidLiuXh
17

pr-address-comments

Summarize open GitHub Pull Request review threads and prompt for fixes.

Community
Intermediate
furkankoykiranfurkankoykiran
4

pr-followup

Fetch GitHub pull request context and prioritize review feedback.

Community
Intermediate
OirancaOiranca

ci-checks

Executes lint, type-check, test, and build commands for CI validation.

Community
Intermediate
rogsmerogsme

create-pr

Create GitHub pull requests after running lint, typecheck, and test checks.

Community
Advanced