pr-checklist

Verify code changes against repository contribution requirements before pull request submission.

75|21|Updated Jan 28, 2026
One-click install
npx skills add https://github.com/yhk1038/claude-code-gui-jetbrains --skill pr-checklist-yhk1038
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-checklist
Source: https://github.com/yhk1038/claude-code-gui-jetbrains/tree/main/.claude/skills/pr-checklist
Command: npx skills add https://github.com/yhk1038/claude-code-gui-jetbrains --skill pr-checklist-yhk1038

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers avoid failed pull requests by systematically checking branch readiness, required documentation, API restrictions, testing status, and project conventions before opening or updating a PR.

Core Features & Use Cases

  • PR Readiness Verification: Checks rebasing status, feature documentation requirements, marketplace API restrictions, test layers, and contribution rules.
  • Quality and Compliance Checks: Reviews cross-platform concerns, naming consistency, CLI equivalence, and data preservation principles.
  • Use Case: A contributor finishing a JetBrains plugin feature can use this Skill to confirm the branch meets repository standards before submitting a pull request.

Quick Start

Ask the AI to run the PR checklist and report whether the current changes are ready for submission.

Frequently Asked Questions about pr-checklist

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

FAQPage Schema
How do I verify code changes are ready for a pull request submission?

To verify code changes are ready for a pull request, validate rebasing status, required documentation updates, API usage restrictions, test execution, and project-specific engineering principles before opening the PR.

What is included in a pull request readiness check for a JetBrains plugin?

A pull request readiness check for a JetBrains plugin includes verifying cross-platform compatibility, naming consistency, CLI equivalence, feature documentation, and data preservation principles.

How do I check branch contribution requirements before opening a PR?

Check branch contribution requirements by validating repository quality gates, testing status, marketplace API restrictions, and ensuring all project conventions are met before opening a PR.

Does this PR validation process apply to general git workflows or only specific platforms?

This PR validation process applies to general developer workflows involving PR preparation, feature contributions, branch validation, and release readiness reviews across different project environments.

What should I do if my feature branch fails repository contribution rules?

If your feature branch fails repository contribution rules, review test execution status, update feature documentation, verify API restrictions, and ensure cross-platform compatibility before resubmitting.