What is prepare-pull-request?

A pull-request preparation workflow for finalising code changes and opening a review request. A pull request is a request for teammates to inspect and merge a branch into the main codebase.

Use it to prepare feature branches, run repository or package tests, organise Conventional Commits, and create a complete pull request.

It provides a repository-aware checklist for updating the branch, running lint and tests, following commit conventions, and filling in the review description. This reduces missed checks before review.

How felipebarcelospro/igniter-js configures GitHub Copilot

Reuse

Borrowing it

Nothing to install: this file belongs to felipebarcelospro/igniter-js. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/felipebarcelospro/igniter-js/main/.github/prompts/prepare-pull-request.md

Clone the repo

git clone --depth 1 https://github.com/felipebarcelospro/igniter-js

Made for: GitHub Copilot.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/commands/felipebarcelospro/igniter-js/prepare-pull-request/github.svg)](https://agentmods.dev/commands/felipebarcelospro/igniter-js/prepare-pull-request)

Your own site

<a href="https://agentmods.dev/commands/felipebarcelospro/igniter-js/prepare-pull-request"><img src="https://agentmods.dev/badge/commands/felipebarcelospro/igniter-js/prepare-pull-request/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/commands/felipebarcelospro/igniter-js/prepare-pull-request"><img src="https://agentmods.dev/badge/commands/felipebarcelospro/igniter-js/prepare-pull-request.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 597 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00000	$0.00597
Opus 5.5	$0.00000	$0.00239
Sonnet 5.5	$0.00000	$0.00119
Haiku 4.5	$0.00000	$0.00060

Measured 1mo ago against content hash 38727e51b629, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

prepare-pull-request scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.github/prompts/prepare-pull-request.md · 56 lines

How it starts

The opening of the file, as written. The whole thing — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Prompt: Prepare Pull Request (Follow Repository Templates)

Purpose

Standardize the process of finalizing work and opening a high-quality Pull Request (PR) that adheres to this repository's templates and conventions. Ensure code quality gates are satisfied, commits use Conventional Commits, and the PR description is complete and helpful for reviewers.

Prerequisites

Ensure all local changes are saved.
Confirm tests and lint pass locally for all affected packages.
Verify you are on a feature branch (not main). If not, create one.

Step-by-Step Instructions

Sync and Branch Hygiene
- Fetch latest changes: git fetch --all --prune.
- Rebase or merge latest main into the working branch as appropriate.
- Confirm a descriptive branch name (e.g., feat/core-middleware-chaining).
Lint & Test
- Run monorepo lint: npm run lint.
- Run tests for all packages: npm run test.
- If only some packages changed, run scoped tests: npm test --filter <pkg>.
- Fix any issues before proceeding.
Create Conventional Commits
- Use the create-conventional-commits prompt to analyze all changes, group them into atomic commits, and generate Conventional Commit messages with scopes.
- Ensure each commit message is in English and uses the correct scope (e.g., core, cli, adapter-redis, www, repo).
Summarize Changes
- Gather the list of commits since the branch diverged from main.
- Categorize commits by type: Features, Fixes, Docs, Refactor, Perf, Tests, Build, CI, Chore, and Breaking Changes.
Build PR Title & Description Using Template
- Title:
  - Prefer an imperative, succinct summary (e.g., feat(core): add middleware chaining support).
- Description:
  - Follow .github/PULL_REQUEST_TEMPLATE.md sections.
  - Include: Context/Problem, Solution, Screenshots/Logs (if UI), Breaking Changes, Checklist.
  - Link related issues (e.g., Closes #123).
Preview & Approval
- Show the proposed PR title and fully rendered description for review.
- Ask for approval to open the PR.

Read the full file on GitHub · 56 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

1mo ago First seen · 56 lines · 0 tokens per session scan A 38727e51b629

Subscribe to this mod's changes

prepare-pull-request is a command published in the GitHub repository felipebarcelospro/igniter-js (240 stars, last pushed 29d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 597 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-27.

Code review Commits Git and workflow api express fastify framework http middleware

prepare-pull-request next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
prepare-pull-requestfelipebarcelospro/igniter-js	Command	240	29d ago	Apache-2.0	A	0	GitHub Copilot
elegant-code-reviewathola/claude-night-market	Command	348	yesterday	MIT	A	27	Claude Code
prp-commitFmarzochi/EGC	Command	68	yesterday	Apache-2.0	A	15	Claude Code
gsd:pr-branchkryptobaseddev/cleo	Command	160	today	MIT	A	24	Claude Code
validate-pr-descriptionrjmurillo/ai-agents	Command	49	yesterday	MIT	A	22	Claude Code
karpathy-checkricneves-ai/flowgrammers-skills	Command	117	1mo ago	MIT	A	0	Claude Code
reviewSwiftfulThinking/SwiftfulStarterProject	Command	73	10d ago	MIT	A	12	Claude Code

igniter-js: Command for GitHub Copilot