skills.rest
aberrantCode
aberrantCodeCOMMUNITY
Explore all skills by this author →
GitHub

homeradar-pre-pr

Automate the HomeRadar pre-PR gate sequence for API, Extension, and Web stacks.

1|Updated Feb 26, 2026
Search Tags:#testing#gate#ci#pull-request#spec-coverage#pre-pr#homeradar
One-click install
npx skills add https://github.com/aberrantCode/llm_skills --skill homeradar-pre-pr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: homeradar-pre-pr
Source: https://github.com/aberrantCode/llm_skills/tree/main/claude/skills/pre-pr
Command: npx skills add https://github.com/aberrantCode/llm_skills --skill homeradar-pre-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The HomeRadar pre-PR gate ensures three sequential checks are completed before a pull request can be opened.

Core Features & Use Cases

  • Orchestrates the three gates (Test Gate, Quality Gate, Spec Gate) for touched stacks.
  • Enforces gating order and provides clear pass/fail criteria to guide PR authors and reviewers.
  • Validates that PR descriptions include a Spec Coverage mapping and supports quick re-run of gates when changes occur.

Quick Start

Invoke homeradar:pre-pr and follow the prompts to ensure all gates pass before opening the PR.

Frequently Asked Questions about homeradar-pre-pr

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

FAQPage Schema
How do I automate pre-PR checks for test, quality, and spec coverage gates?▼

Pre-PR gate validation enforces three sequential checks (Test, Quality, Spec) across touched stacks before opening a pull request. It coordinates test execution, quality checks, and spec coverage validation across API, Extension, and Web stacks to prevent unreviewed failures.

What is spec coverage mapping in a pull request?▼

Spec coverage mapping validates that a pull request description includes explicit links between code changes and specifications. It is enforced as the final gate before PR submission to ensure touched stacks meet defined requirements.

How do I run pre-PR gates for touched stacks across API, Extension, and Web?▼

Running pre-PR gates requires invoking the gate sequence and following prompts to execute Test, Quality, and Spec gates sequentially. The gates coordinate test execution, quality checks, and spec validation across touched stacks to ensure all pass before PR submission.

Why does my pre-PR gate sequence fail when I skip the test gate?▼

Pre-PR gate sequences fail when skipped because the system enforces strict gate ordering. Test, Quality, and Spec gates must pass sequentially, and skipping any gate prevents validation of required commands and spec coverage mapping before PR submission.

Can I re-run specific pre-PR quality gates when changes occur in touched stacks?▼

You can re-run pre-PR gates when changes occur to quickly validate touched stacks. The gate sequence supports quick re-runs of Test, Quality, and Spec gates, ensuring updated code passes required checks before opening the pull request.

Does the pre-PR gate validate pull requests for all stack types?▼

The pre-PR gate validates pull requests for touched stacks across API, Extension, and Web. It applies the three sequential gates (Test, Quality, Spec) to these stack types to ensure comprehensive coverage before submission.

Related Skills

Explore More Software Engineering Skills→
thoreinsteinthoreinstein
5

add-test-coverage

Analyze the latest HEAD commit and generate a test coverage plan.

Community
Advanced
mfittkomfittko
14

final-approval

Route dev loop execution to the canonical final approval and merge gate procedure.

Community
Basic
DevelopersGlobalDevelopersGlobal
65

ci-cd-pipelines

Automate CI/CD pipelines with quality gates and deployment processes.

Official
Advanced
axone-protocolaxone-protocol
124

rust-quality-gates

Execute Rust project quality gates for format, lint, tests, coverage, schema, and docs.

Official
Intermediate