create-pr

Run tests, lint, commit, push, and open a pull request against main.

1|Updated Mar 6, 2026
One-click install
npx skills add https://github.com/gcko/pendulum-of-despair --skill create-pr-gcko
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-pr
Source: https://github.com/gcko/pendulum-of-despair/tree/main/.claude/skills/create-pr
Command: npx skills add https://github.com/gcko/pendulum-of-despair --skill create-pr-gcko

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill streamlines code collaboration by automating the full pull request workflow—from validation to PR creation—so teams can move from changes to review without manual, repetitive steps.

Core Features & Use Cases

  • Automated validation: run tests and lint to ensure code quality before submission.
  • End-to-end PR creation: commit changes, push to the feature branch, and open a PR against main.
  • Use Case: when a feature is complete and ready for review, this skill performs all steps and returns the PR URL for handoff.

Quick Start

Invoke /create-pr once your work is ready to be opened as a pull request.

Frequently Asked Questions about create-pr

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

FAQPage Schema
How do I automate my pull request workflow from running tests to pushing commits?

Automating the pull request workflow involves running tests and linting, committing changes, and pushing to a feature branch. This skill performs these steps end-to-end and opens a PR against main using the GitHub CLI.

What is the best way to run tests, lint, and open a GitHub pull request in one step?

The best way to run tests, lint, and open a GitHub pull request in one step is using an automated workflow. This skill validates code with pnpm, commits, pushes, and returns the PR URL for immediate handoff.

Do I need the GitHub CLI and pnpm installed to automate PR creation?

Yes, you need the GitHub CLI and pnpm tooling installed to automate PR creation. Local Git is also required to execute the end-to-end workflow of committing, pushing, and opening the pull request against main.

How does an automated pull request workflow handle code quality checks before pushing?

An automated pull request workflow handles code quality by running validation steps before submission. This skill specifically executes tests and linting using pnpm to ensure code quality prior to committing and pushing the changes.

Can I use this automated PR workflow if my project does not use pnpm for tests and lint?

No, you cannot use this automated PR workflow if your project does not use pnpm. The skill explicitly requires pnpm tooling to execute its automated validation steps for running tests and linting before submission.