Run any Skill in Manus with one click

pr

Stars221

Forks28

UpdatedJune 26, 2026 at 21:25

Run a pre-PR quality gate (tests, typecheck, lint, code review) and then create a pull request with a structured summary. Use when the user says "create a PR", "open a PR", "submit for review", or "I'm done with this feature".

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

bdfinst

bdfinst/agentic-dev-team

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

SKILL.md

readonly

name	pr
description	Run a pre-PR quality gate (tests, typecheck, lint, code review) and then create a pull request with a structured summary. Use when the user says "create a PR", "open a PR", "submit for review", or "I'm done with this feature".
argument-hint	[--skip-review] [--draft] [--base <branch>]
user-invocable	true
allowed-tools	Read, Write, Edit, Glob, Grep, Bash(git ), Bash(gh ), Bash(npm ), Bash(npx ), Bash(pnpm ), Bash(yarn ), Bash(make ), Bash(pytest ), Bash(go ), Bash(cargo ), Bash(dotnet ), Skill(code-review )

Pull Request

Role: orchestrator. This command enforces quality gates before creating a PR.

You have been invoked with the /pr command.

Orchestrator constraints

Run the quality gate and open the PR; do not bypass failing gates.
Delegate review to the review agents; do not review code yourself.
Be concise. Report gate results and the PR URL, no preamble.

Parse Arguments

Arguments: $ARGUMENTS

--skip-review: Skip the /code-review step (not recommended)
--draft: Create a draft PR
--base <branch>: Target branch (default: main)
--no-auto-merge: Do not enable auto-merge (the default is to enable it; see Step 5)

Steps

1. Pre-flight checks

Verify:

Current branch is not main or master
There are commits ahead of the base branch
Working tree is clean (no uncommitted changes) — if dirty, ask whether to commit or stash

If a plan file is present (check plans/ for the most recently modified approved or implemented plan), run the plan completion gate:

python3 scripts/progress_guardian.py --pre-pr --plan <plan-file>

A non-zero exit means incomplete steps remain; stop and surface the findings — do not open the PR until all steps are [x].

2. Run quality gate

Run each check sequentially. Stop on first failure:

Tests: Detect and run the project's test suite
- package.json scripts: npm test or pnpm test or yarn test
- pytest.ini / pyproject.toml: pytest
- go.mod: go test ./...
- Cargo.toml: cargo test
- *.csproj: dotnet test
- Makefile with test target: make test
Type check (if applicable):
- tsconfig.json: npx tsc --noEmit
- mypy.ini / pyproject.toml with mypy: mypy .
Lint (if applicable):
- eslint in deps: npx eslint .
- ruff available: ruff check .
- golangci-lint available: golangci-lint run
Code review (unless --skip-review):
- Run /code-review --json. /pr owns the human gate, so code-review runs non-interactively: it skips its own "fix or report?" prompt and applies its fix loop automatically (up to 5 iterations), then returns an aggregated status.
- Read the returned status field. A normal review returns {"overall": "pass|warn|fail", ...}; a documentation-only changeset short-circuits with {"status": "skipped", ...}:
  - overall of pass / warn, or status of skipped → continue to step 3.
  - overall of fail → show the remaining findings and ask the user whether to proceed anyway or stop and fix.

Report results as a checklist:

## Quality Gate
- [x] Tests pass (42 passed, 0 failed)
- [x] Type check clean
- [x] Lint clean
- [ ] Code review: 2 warnings (see below)

3. Generate PR summary

Analyze the diff against the base branch (git diff <base>...HEAD) and commit history to generate:

Title: Short, imperative (<70 chars)
Summary: 1-3 bullet points of what changed and why
Test plan: How to verify the changes

4. Create the PR

gh pr create --title "<title>" --body "<body>" [--draft] --base <base>

Use the structured template:

## Summary
- <bullet 1>
- <bullet 2>

## Quality Gate
- [x] Tests: <N> passed
- [x] Type check: clean
- [x] Lint: clean
- [x] Code review: <status>

## Test Plan
- [ ] <verification step 1>
- [ ] <verification step 2>

5. Enable auto-merge (default)

Unless --no-auto-merge or --draft was given, enable auto-merge so the PR lands automatically once checks pass and any required reviews are in — rather than merging directly to trunk. This is the default integration stance in knowledge/decision-defaults.md (auto-merge vs. direct-to-trunk).

gh pr merge --auto --squash

If the repository does not have auto-merge enabled (the command errors), report that and leave the PR open for manual merge — do not merge directly to trunk to work around it.

6. Report

Display the PR URL and a summary of the quality gate results.

If any gate failed and the user chose to proceed anyway, note this in the PR body as a caveat.

More from this repository

same repository

mutation-testing

bdfinst/agentic-dev-team

Validate test suite quality by running a real mutation testing tool and triaging surviving mutants. Use after writing tests to verify assertions catch behavioral changes, when evaluating test coverage quality, or as a CI quality gate on critical modules. The AI value here is triage — classifying survivors, writing fix tests — not generating or estimating mutations.

2026-06-30221

test-upgrade

bdfinst/agentic-dev-team

General-purpose analyze-then-improve test workflow for any JS/TS, Go, Java, or C# codebase. A 4-phase orchestrator: analyze with /test-health, optionally derive Gherkin with /gherkin-derive, triage into work items, implement each Story with /build + /coverage-delta + the mutation-kill agent, and validate with /quality-targets-converge. Local-first, BDD optional, Go-aware. Use when the user says "upgrade our tests", "improve test quality", or runs /test-upgrade. Lighter and general-purpose where /test-modernize is a brownfield legacy rescue.

2026-06-30221

frontend-architecture

bdfinst/agentic-dev-team

Frontend component architecture review — dispatch the component-architecture-review agent over the frontend component files to catch reusable components that should be extracted, duplicated UI patterns, prop drilling, component-granularity problems, and inconsistent component APIs as a frontend evolves. Use when the user says "review the frontend architecture", "are my components reusable", "is this UI duplicated", "should this be a shared component", "check for prop drilling", or before extracting a component library. Advisory — it recommends, it does not edit.

2026-06-28221

agent-eval

bdfinst/agentic-dev-team

Run eval fixtures against review agents and grade results. Use this after adding or modifying a review agent, to validate detection accuracy, or when the user says "run the evals", "test the agents", "check for regressions", or "how accurate is the agent".

2026-06-27221

code-review

bdfinst/agentic-dev-team

Run all enabled review agents against target files. Use this whenever the user asks for a code review, wants feedback on their code, says "review my code", "check this before I PR", "what's wrong with this", "run the agents", or has just finished implementing a feature. Use proactively before commits and pull requests.

2026-06-27221

explore

bdfinst/agentic-dev-team

Charter-driven exploratory testing of a running feature or endpoint. Dispatches the QA Engineer in "Chaos Specialist" mode to probe with structured heuristics (Goldilocks, Happy-Path Divergence, Telemetry Deepening, Invariant Probing, CRUD Sweep), run adversarial expansion, and auto-triage critical defects into an incremental report. Use when the user says "explore this endpoint", "poke at this feature", or wants hands-off exploratory testing of a live target.

2026-06-27221

name	pr
description	Run a pre-PR quality gate (tests, typecheck, lint, code review) and then create a pull request with a structured summary. Use when the user says "create a PR", "open a PR", "submit for review", or "I'm done with this feature".
argument-hint	[--skip-review] [--draft] [--base <branch>]
user-invocable	true
allowed-tools	Read, Write, Edit, Glob, Grep, Bash(git ), Bash(gh ), Bash(npm ), Bash(npx ), Bash(pnpm ), Bash(yarn ), Bash(make ), Bash(pytest ), Bash(go ), Bash(cargo ), Bash(dotnet ), Skill(code-review )

Pull Request

Role: orchestrator. This command enforces quality gates before creating a PR.

You have been invoked with the /pr command.

Orchestrator constraints

Run the quality gate and open the PR; do not bypass failing gates.
Delegate review to the review agents; do not review code yourself.
Be concise. Report gate results and the PR URL, no preamble.

Parse Arguments

Arguments: $ARGUMENTS

--skip-review: Skip the /code-review step (not recommended)
--draft: Create a draft PR
--base <branch>: Target branch (default: main)
--no-auto-merge: Do not enable auto-merge (the default is to enable it; see Step 5)

Steps

1. Pre-flight checks

Verify:

Current branch is not main or master
There are commits ahead of the base branch
Working tree is clean (no uncommitted changes) — if dirty, ask whether to commit or stash

If a plan file is present (check plans/ for the most recently modified approved or implemented plan), run the plan completion gate:

python3 scripts/progress_guardian.py --pre-pr --plan <plan-file>

A non-zero exit means incomplete steps remain; stop and surface the findings — do not open the PR until all steps are [x].

2. Run quality gate

Run each check sequentially. Stop on first failure:

Tests: Detect and run the project's test suite
- package.json scripts: npm test or pnpm test or yarn test
- pytest.ini / pyproject.toml: pytest
- go.mod: go test ./...
- Cargo.toml: cargo test
- *.csproj: dotnet test
- Makefile with test target: make test
Type check (if applicable):
- tsconfig.json: npx tsc --noEmit
- mypy.ini / pyproject.toml with mypy: mypy .
Lint (if applicable):
- eslint in deps: npx eslint .
- ruff available: ruff check .
- golangci-lint available: golangci-lint run
Code review (unless --skip-review):
- Run /code-review --json. /pr owns the human gate, so code-review runs non-interactively: it skips its own "fix or report?" prompt and applies its fix loop automatically (up to 5 iterations), then returns an aggregated status.
- Read the returned status field. A normal review returns {"overall": "pass|warn|fail", ...}; a documentation-only changeset short-circuits with {"status": "skipped", ...}:
  - overall of pass / warn, or status of skipped → continue to step 3.
  - overall of fail → show the remaining findings and ask the user whether to proceed anyway or stop and fix.

Report results as a checklist:

## Quality Gate
- [x] Tests pass (42 passed, 0 failed)
- [x] Type check clean
- [x] Lint clean
- [ ] Code review: 2 warnings (see below)

3. Generate PR summary

Analyze the diff against the base branch (git diff <base>...HEAD) and commit history to generate:

Title: Short, imperative (<70 chars)
Summary: 1-3 bullet points of what changed and why
Test plan: How to verify the changes

4. Create the PR

gh pr create --title "<title>" --body "<body>" [--draft] --base <base>

Use the structured template:

## Summary
- <bullet 1>
- <bullet 2>

## Quality Gate
- [x] Tests: <N> passed
- [x] Type check: clean
- [x] Lint: clean
- [x] Code review: <status>

## Test Plan
- [ ] <verification step 1>
- [ ] <verification step 2>

5. Enable auto-merge (default)

gh pr merge --auto --squash

If the repository does not have auto-merge enabled (the command errors), report that and leave the PR open for manual merge — do not merge directly to trunk to work around it.

6. Report

Display the PR URL and a summary of the quality gate results.

If any gate failed and the user chose to proceed anyway, note this in the PR body as a caveat.