pr-integration-gate

Enforce build, test, and configuration checks for pull requests targeting the dev branch.

1|Updated Jul 16, 2023
One-click install
npx skills add https://github.com/jmservera/aithena --skill pr-integration-gate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-integration-gate
Source: https://github.com/jmservera/aithena/tree/main/.squad/skills/pr-integration-gate
Command: npx skills add https://github.com/jmservera/aithena --skill pr-integration-gate

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents broken builds and test failures in the dev branch by enforcing essential pre-merge checks for different types of Pull Requests.

Core Features & Use Cases

  • Frontend PR Validation: Verifies frontend builds and linting.
  • Backend PR Validation: Ensures backend tests pass and code compiles.
  • Infrastructure Validation: Checks Docker and Nginx configurations.
  • Use Case: Before merging a frontend change, run npm run build and npm run lint to catch errors early, preventing UI breakages.

Quick Start

Run the pr-integration-gate skill to verify frontend changes in the aithena-ui directory.

Frequently Asked Questions about pr-integration-gate

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

FAQPage Schema
How do I enforce pre-merge quality checks for pull requests targeting the dev branch?

To enforce pre-merge quality checks for pull requests targeting the dev branch, you can validate frontend builds, backend pytest suites, and infrastructure Docker configurations to prevent broken integrations.

What is the best way to prevent broken builds and test failures in a dev branch?

Preventing broken builds and test failures in a dev branch requires enforcing mandatory build, test, and configuration checks across frontend, backend, and infrastructure components before merging pull requests.

How do I validate frontend and backend changes before merging a pull request?

To validate frontend and backend changes before merging a pull request, run npm run build and npm run lint for frontend components, and execute pytest and compilation checks for backend components.

Does this pre-merge validation process check infrastructure configurations like Docker and Nginx?

Yes, this pre-merge validation process checks infrastructure configurations by validating Docker and Nginx configurations to prevent integration issues when infrastructure changes are merged.

Can I use this pull request validation for multiple component types in my workflow?

Yes, you can use this pull request validation for multiple component types in your workflow, as it supports specific command-line verifications across frontend, backend, and infrastructure components.

What specific command-line verifications are required for frontend PR validation?

The specific command-line verifications required for frontend PR validation are running npm run build to catch build errors and npm run lint to ensure linting passes before merging UI changes.