Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

pr-check

Sterne3

Forks1

Aktualisiert26. Februar 2026 um 21:05

Validate that a pull request follows principled conventions: references a plan or proposal, has correct labels, includes required sections in the description, and links to relevant documents. Use in CI or before merging to enforce PR quality.

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

In Manus ausführen

Quelle

alexnodeland

alexnodeland/principled

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

In Manus ausführen

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

Softwarequalitätssicherungsanalysten und -testerInformatik- und Mathematikberufe·SOC 15-1253

Datei-Explorer

4 Dateien

SKILL.md

readonly

name	pr-check
description	Validate that a pull request follows principled conventions: references a plan or proposal, has correct labels, includes required sections in the description, and links to relevant documents. Use in CI or before merging to enforce PR quality.
allowed-tools	Read, Bash(gh ), Bash(git ), Bash(bash plugins/*)
user-invocable	true

PR Check --- Pull Request Validation

Validate that a pull request follows principled conventions for cross-referencing, labeling, and description quality.

Command

/pr-check [<pr-number>] [--strict] [--json]

Arguments

Argument	Required	Description
`<pr-number>`	No	PR number to check. Defaults to the current branch's open PR.
`--strict`	No	Fail on warnings (by default, only errors cause failure).
`--json`	No	Output results as JSON instead of human-readable text.

Prerequisites

gh CLI must be installed and authenticated
For default behavior (no PR number): current branch must have an open PR

Workflow

Resolve PR. Determine which PR to check:
- If <pr-number> provided: use it directly
- Otherwise: find the PR for the current branch via gh pr view --json number
- If no PR found: report error and exit
Fetch PR metadata. Get PR details:
```
bash scripts/fetch-pr-metadata.sh --pr <number>
```
Returns: title, body, labels, base branch, head branch, file count, and file paths.
Run checks. Execute each validation:
```
bash scripts/validate-pr.sh --pr-body "<body>" --pr-labels "<labels>" --branch "<head-branch>" --files "<files>" [--strict]
```
The script checks:

Required (errors):
- PR body is not empty
- PR body contains a ## Summary section
- PR body contains a ## Test plan or ## Checklist section
Recommended (warnings, errors in --strict):
- PR body references at least one GitHub issue (Closes #N, Fixes #N, Relates to #N)
- PR references a plan (Plan-NNN) or proposal (RFC-NNN)
- PR has at least one principled label (type:*, plan:*, proposal:*)
- Branch name follows a recognized convention (impl/, feat/, fix/)
- Files changed include tests if source files were modified
Report results. Display check results:
- Each check with pass/warn/fail status
- Overall result: pass or fail
- If --json: structured JSON output
- Exit code 0 for pass, 1 for fail

Scripts

scripts/check-gh-cli.sh --- Verify gh CLI availability (copy)
scripts/fetch-pr-metadata.sh --- Fetch PR details from GitHub
scripts/validate-pr.sh --- Run PR validation checks

Mehr aus diesem Repository

gleiches Repository

pr-describe

alexnodeland/principled

Generate a structured pull request description from a DDD plan task. Reads the plan, task manifest, and implementation branch to produce a PR body with references to the originating proposal, plan, ADRs, and related tasks. Use when opening a PR for plan-driven work.

2026-02-263

triage

alexnodeland/principled

Process open GitHub issues through the principled pipeline. Lists untriaged issues, normalizes their metadata, ingests them into the documentation pipeline, and reports a summary. Operates as the batch entry point — delegates to /ingest-issue for each individual issue.

2026-02-263

impl-strategy

alexnodeland/principled

Implementation orchestration strategy for the Principled framework. Consult when working with DDD plan execution, git worktrees for task isolation, task manifests, or the decompose-spawn-validate-merge lifecycle. Covers worktree management, sub-agent patterns, task state machines, and manifest schema.

2026-02-233

orchestrate

alexnodeland/principled

Top-level orchestrator for DDD plan execution. Decomposes a plan into tasks, iterates through phases respecting dependencies, spawns worktree-isolated agents, validates implementations, and merges results. Runs inline to coordinate multiple sub-agent spawns. Use for automated end-to-end plan execution.

2026-02-233

arch-audit

alexnodeland/principled

Audit ADR coverage across modules. Identifies modules with no architectural governance, orphaned ADRs referencing removed modules, and stale architecture docs. Classifies findings by severity.

2026-02-233

arch-drift

alexnodeland/principled

Detect violations of architectural decisions in the codebase. Checks module dependency direction rules, identifies boundary violations, and reports drift between documented decisions and actual code.

2026-02-233

name	pr-check
description	Validate that a pull request follows principled conventions: references a plan or proposal, has correct labels, includes required sections in the description, and links to relevant documents. Use in CI or before merging to enforce PR quality.
allowed-tools	Read, Bash(gh ), Bash(git ), Bash(bash plugins/*)
user-invocable	true

PR Check --- Pull Request Validation

Validate that a pull request follows principled conventions for cross-referencing, labeling, and description quality.

Command

/pr-check [<pr-number>] [--strict] [--json]

Arguments

Argument	Required	Description
`<pr-number>`	No	PR number to check. Defaults to the current branch's open PR.
`--strict`	No	Fail on warnings (by default, only errors cause failure).
`--json`	No	Output results as JSON instead of human-readable text.

Prerequisites

gh CLI must be installed and authenticated
For default behavior (no PR number): current branch must have an open PR

Workflow

Resolve PR. Determine which PR to check:
- If <pr-number> provided: use it directly
- Otherwise: find the PR for the current branch via gh pr view --json number
- If no PR found: report error and exit
Fetch PR metadata. Get PR details:
```
bash scripts/fetch-pr-metadata.sh --pr <number>
```
Returns: title, body, labels, base branch, head branch, file count, and file paths.
Run checks. Execute each validation:
```
bash scripts/validate-pr.sh --pr-body "<body>" --pr-labels "<labels>" --branch "<head-branch>" --files "<files>" [--strict]
```
The script checks:

Required (errors):
- PR body is not empty
- PR body contains a ## Summary section
- PR body contains a ## Test plan or ## Checklist section
Recommended (warnings, errors in --strict):
- PR body references at least one GitHub issue (Closes #N, Fixes #N, Relates to #N)
- PR references a plan (Plan-NNN) or proposal (RFC-NNN)
- PR has at least one principled label (type:*, plan:*, proposal:*)
- Branch name follows a recognized convention (impl/, feat/, fix/)
- Files changed include tests if source files were modified
Report results. Display check results:
- Each check with pass/warn/fail status
- Overall result: pass or fail
- If --json: structured JSON output
- Exit code 0 for pass, 1 for fail

Scripts

scripts/check-gh-cli.sh --- Verify gh CLI availability (copy)
scripts/fetch-pr-metadata.sh --- Fetch PR details from GitHub
scripts/validate-pr.sh --- Run PR validation checks