skills.rest
guardiatechnology
guardiatechnologyOFFICIAL
Explore all skills by this author →
WebsiteGitHub

kata-pr-prepare

Prepare and open GitHub Pull Requests with Conventional Commit messages and traceability.

Updated Sep 3, 2025
Search Tags:#automation#code review#pull request#github#mcp#issue-driven development#adr management
One-click install
npx skills add https://github.com/guardiatechnology/design-system --skill kata-pr-prepare
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: kata-pr-prepare
Source: https://github.com/guardiatechnology/design-system/tree/main/.claude/skills/kata-pr-prepare
Command: npx skills add https://github.com/guardiatechnology/design-system --skill kata-pr-prepare

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the coordination gap between code changes and a fully traceable, policy-compliant GitHub Pull Request by automating branch creation, pushes, PR composition, and required QA/ADR/issue state transitions.

Core Features & Use Cases

  • Branch + PR orchestration: Creates a correctly named branch and PR, pushes all modified files with Conventional Commit messages, and links the PR to the originating issue.
  • Structured PR body with traceability: Generates a consistent PR body referencing the Gate 2 quality report, architecture/requirements artifacts, and session trace data.
  • Quality guardrails before review: Enforces an inviolable Gate 2 “go/no-go” prerequisite, runs up to three Argos pre-flight review cycles (with explicit user confirmation), handles P0/P1 findings, and supports CHANGES_REQUESTED resets.
  • Human review escalation loop: Schedules up to three timed nudges with Slack notifications (or supports manual/remote scheduling) and reacts to APPROVED vs CHANGES_REQUESTED outcomes.
  • ADR lifecycle + checkpoint updates: Transitions ADRs from proposed to accepted and updates the final workflow checkpoint with PR URL, branch, and completion status.

Quick Start

Use kata-pr-prepare to prepare and open a GitHub PR for a given issue after a Gate 2 quality report returns go, ensuring the PR body references the corresponding .ahrena artifacts and that ADR/checkpoint states are updated.

Frequently Asked Questions about kata-pr-prepare

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

FAQPage Schema
How do I automate opening a GitHub pull request with issue traceability?▼

Automating a GitHub pull request with issue traceability requires orchestrating branch creation, file pushes, and structured PR body generation linked to originating issues. This workflow enforces MCP-based operations and Conventional Commit messages for consistent, policy-compliant PRs.

How do I generate a structured PR body that links to quality reports and artifacts?▼

Generating a structured PR body linked to quality reports involves referencing Gate 2 quality outputs, architecture artifacts, and session trace data. This ensures the pull request maintains full traceability to .ahrena/issues/{n} artifacts for comprehensive review.

What is the Gate 2 go/no-go prerequisite before opening a pull request?▼

The Gate 2 go/no-go prerequisite is an inviolable safety gate that must return a go status before pull request preparation begins. It enforces pre-flight quality cycles, handles P0/P1 findings, and supports CHANGES_REQUESTED resets to ensure code readiness.

Can I use Conventional Commit conventions for automated branch and PR creation?▼

Yes, using Conventional Commit conventions for automated branch and PR creation ensures correctly named branches and structured commit messages. This approach applies MCP-based GitHub operations to push modified files while linking the PR to the originating issue.

How do I schedule human review nudges for a pull request via Slack notifications?▼

Scheduling human review nudges via Slack notifications involves setting up to three timed reminders that escalate pull request reviews. The system reacts to APPROVED or CHANGES_REQUESTED outcomes and supports manual or remote scheduling for flexible review management.

How do I transition ADRs from proposed to accepted after opening a pull request?▼

Transitioning ADRs from proposed to accepted after opening a pull request requires updating the final workflow checkpoint with the PR URL, branch name, and completion status. This lifecycle management ensures architecture decisions reflect implemented code changes.

Related Skills

Explore More Software Engineering Skills→
guardiatechnologyguardiatechnology

kata-quality-gate

Validate implementations against acceptance criteria and quality gates, persisting reports to .ahrena.

Official
Advanced
aaddrickaaddrick
125

process-pr

Processes GitHub PRs by evaluating comment-based review status and executing CLI actions.

Community
Advanced
softsparksoftspark
161

pr

Create GitHub pull requests with pre-flight validation and automated commit summaries.

Community
Intermediate
christian289christian289

managing-branch-pr-workflow

Enforce branch naming, commit message formatting, and automated pull request creation.

Community
Intermediate