skills.rest
ebenfc
ebenfcCOMMUNITY
Explore all skills by this author →
GitHub

pr-ready

Run tests, linting, and type-checking, verify CLAUDE.md updates, and create a pull request via GitHub CLI.

Updated Aug 23, 2026
Search Tags:#automation#testing#code review#linting#github#pr
One-click install
npx skills add https://github.com/ebenfc/bird-photo-gallery --skill pr-ready-ebenfc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-ready
Source: https://github.com/ebenfc/bird-photo-gallery/tree/main/.claude/skills/pr-ready
Command: npx skills add https://github.com/ebenfc/bird-photo-gallery --skill pr-ready-ebenfc

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the entire pre-pull request checklist and PR creation process, ensuring code quality and consistency before submission for review.

Core Features & Use Cases

  • Automated Checks: Runs tests, linting, and type-checking in parallel.
  • Documentation Verification: Guides you to update CLAUDE.md files based on code changes.
  • PR Creation: Generates a well-formatted pull request using the GitHub CLI.
  • Use Case: Before submitting your code for review, run this skill to automatically verify all checks pass, ensure documentation is up-to-date, and create a clean pull request with a descriptive title and body.

Quick Start

Use the pr-ready skill to prepare your code and create a pull request.

Frequently Asked Questions about pr-ready

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

FAQPage Schema
How do I automate my pre-pull request checklist for testing and linting?▼

To automate your pre-pull request checklist, you can run tests, linting, and type-checking in parallel before submitting code for review. This verifies code quality and ensures documentation consistency automatically.

How do I create a pull request using the GitHub CLI after passing code checks?▼

Creating a pull request with the GitHub CLI is handled automatically after tests and linting pass. It generates a well-formatted PR with a descriptive title and body to streamline your workflow.

What is the best way to ensure CLAUDE.md documentation is updated before submitting a PR?▼

To ensure CLAUDE.md documentation is updated before a PR, use an automated documentation verification step. This guides you to update your files based on recent code changes for consistency.

Does the automated PR creation process run type-checking and linting in parallel?▼

Yes, automated checks run tests, linting, and type-checking in parallel. This parallel execution ensures code quality is verified efficiently before pull request creation.

Can I use this PR automation if I don't have the GitHub CLI installed?▼

No, the GitHub CLI is required for the pull request creation feature. The skill depends on it to automatically generate and submit your well-formatted PR after checks pass.

Why should I automate my pull request preparation process instead of running checks manually?▼

Automating pull request preparation prevents human error by running parallel checks and verifying documentation updates. It ensures consistent code quality and documentation before submission, unlike manual verification.

Related Skills

Explore More Software Engineering Skills→
hivellmhivellm
15

rulebook-quality-gates

Enforce automated quality gates on code changes before commits and pushes.

Official
Advanced
taloncjonestaloncjones

ship

Automate code review, testing, version bump, merge, and post-merge cleanup for pull requests.

Community
Advanced
gkganesh12gkganesh12
1

gk-review

Audit source code against documentation and test suites for architectural drift.

Community
Advanced
Tommy-ywTommy-yw
539

github-pr-workflow

Automate GitHub pull request lifecycle from branch creation to merge.

Community
Advanced