pr

Open a GitHub pull request after cleanup, formatting, and test gates.

19|2|Updated Mar 30, 2026
One-click install
npx skills add https://github.com/bjornjee/agent-dashboard --skill pr-bjornjee
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr
Source: https://github.com/bjornjee/agent-dashboard/tree/main/adapters/claude-code/skills/pr
Command: npx skills add https://github.com/bjornjee/agent-dashboard --skill pr-bjornjee

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents broken or messy pull requests by enforcing a consistent cleanup, formatting, and test gate before PR creation.

Core Features & Use Cases

  • Enforced PR creation path: Opens a pull request for the current branch using the required PR-skill bypass marker so the repo’s PR hook gate is satisfied.
  • Deterministic branch hygiene: Removes untracked scratch artifacts (with strict pattern constraints) and runs an AI refactor-cleaner scoped to changed files.
  • Workflow-gated quality checks: Runs make fmt and make test when available (or prompts to add missing targets), and stops on failures to avoid pushing red builds.

Quick Start

Ask your agent to run the pr skill to open a PR for your current branch with cleanup, fmt, and tests gated.

Frequently Asked Questions about pr

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

FAQPage Schema
How do I automate formatting and tests before opening a GitHub pull request?

Automating formatting and tests before opening a GitHub pull request requires a workflow gate that runs make fmt and make test, cleans up scratch artifacts, and stops on failures to prevent pushing red builds. This ensures code quality before merging.

What is the best way to remove untracked files and enforce conventional commits in a PR workflow?

Removing untracked files and enforcing conventional commits in a PR workflow involves applying pattern constraints to delete scratch artifacts and running an AI refactor-cleaner scoped to changed paths. This deterministic branch hygiene prevents messy pull requests.

Can I use gh pr create with automated cleanup and test gates for my current branch?

You can use gh pr create with automated cleanup and test gates by applying a required PR-skill bypass marker like AGENT_DASHBOARD_PR_SKILL=1. This satisfies repo PR hook gates while ensuring formatting and tests pass before creation.

Does this PR automation skill work if my repository is missing make fmt or make test targets?

If your repository is missing make fmt or make test targets, the workflow-gated quality checks will prompt you to add the missing targets. It negotiates adding these targets before attempting to run the formatting and test gates.

Why should I use an automated PR gate instead of manually cleaning up AI code changes?

Using an automated PR gate instead of manual cleanup prevents broken pull requests by enforcing consistent formatting, test verification, and scratch artifact removal. It deterministically scopes refactor cleaning to changed files, avoiding human error.

What happens when make test fails during automated pull request creation?

When make test fails during automated pull request creation, the workflow stops immediately to avoid pushing red builds. This constraint ensures that only verified code changes pass the quality gate and proceed to GitHub.