skills.rest
HypoxanthineOvO
HypoxanthineOvOCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

pr

Archive PR and MR metadata and artifacts into local Change Request workspaces.

24|3|Updated Apr 22, 2026
Search Tags:#workflow#evidence#pr#code-review#change-request#mr#local-archive
One-click install
npx skills add https://github.com/HypoxanthineOvO/Hypo-Workflow --skill pr-hypoxanthineovo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr
Source: https://github.com/HypoxanthineOvO/Hypo-Workflow/tree/main/skills/pr
Command: npx skills add https://github.com/HypoxanthineOvO/Hypo-Workflow --skill pr-hypoxanthineovo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeps PRs and MRs organized within a local Change Request archive, enabling offline planning, review, and audit without depending on remote writes.

Core Features & Use Cases

  • Local Change Request archives: automatically create .pipeline/pr/PR-YYYYMMDD-NNN and store PR/MR metadata and artifacts.
  • Evidence generation: populate request.yaml, summary.md, review-notes.md, changes.md, decisions.yaml, and an evidence folder locally.
  • Safe-by-default workflow: prompts for confirmation before any remote write and normalizes GitHub PR / GitLab MR terminology to Change Request records.

Quick Start

Use /hw:pr inspect, review, fix, merge, close, or create to manage a local Change Request archive for a PR or MR.

Frequently Asked Questions about pr

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

FAQPage Schema
How do I manage PR and MR workflows entirely in a local environment?▼

You archive PR and MR metadata in a dedicated local Change Request workspace under .pipeline/pr. This enables offline planning, review, and audit without requiring immediate remote actions.

Can I review and fix pull requests offline without pushing commits remotely?▼

Yes, the workflow creates local Change Request archives with artifacts like review-notes.md and changes.md. It operates entirely offline and prompts for explicit confirmation before executing any remote write action.

What evidence files are generated when archiving a change request locally?▼

Archiving a change request locally generates request.yaml, summary.md, review-notes.md, changes.md, decisions.yaml, and an evidence folder. These files are automatically populated within the .pipeline/pr/PR-YYYYMMDD-NNN directory structure.

Does the local PR archiving workflow support both GitHub and GitLab terminology?▼

Yes, the workflow normalizes GitHub PR and GitLab MR terminology to unified Change Request records. This standardization ensures consistent local artifact generation across different version control platforms.

How do I prevent accidental remote updates during a local code review process?▼

The safe-by-default workflow prevents accidental remote updates by storing all changes locally and explicitly prompting for user confirmation before initiating any remote write operations.

Related Skills

Explore More Software Engineering Skills→
tachiiri-orgtachiiri-org

setup-dev-github

Create a GitHub repository and initialize main and dev branches.

Official
Intermediate
jfmyers9jfmyers9
8

sync

Synchronize a Git-Spice repository with its remote and trunk.

Community
Intermediate
clevergadgetclevergadget

code-reviewer

Review local changes and remote Pull Requests using Git and GitHub CLI.

Community
Intermediate
nsheapsnsheaps
3

update-branch

Synchronize feature branches with their PR base using git and gh.

Community
Advanced