pull-request

Automate GitHub pull request creation with compliance checks and structured descriptions.

2|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/PequiProject/pequi --skill pull-request-pequiproject
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pull-request
Source: https://github.com/PequiProject/pequi/tree/main/.agents/skills/pull-request
Command: npx skills add https://github.com/PequiProject/pequi --skill pull-request-pequiproject

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manual pull request creation, review coordination, and governance checks slow development and risk drift; this skill automates PR governance to reduce overhead and human error.

Core Features & Use Cases

  • Automated PR descriptions generated from commit history to reflect changes clearly.
  • LGPD, architecture-layer, and testing requirement validation as part of PR eligibility.
  • Enforcement of Conventional Commits and required Bruno API documentation for new endpoints.

Quick Start

Submit a feature branch PR to trigger the automated PR description generator and compliance checks.

Frequently Asked Questions about pull-request

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

FAQPage Schema
How do I automate pull request creation and compliance checks for GitHub workflows?

Automating pull request creation performs pre-flight checks, generates structured PR descriptions from commit history, and enforces compliance with LGPD, architecture layers, and testing requirements. It reduces manual overhead and prevents governance drift in GitHub-based workflows.

What is the best way to generate PR descriptions from conventional commits?

Generating PR descriptions from conventional commits automatically parses your commit history to reflect changes clearly. This automated generation ensures structured descriptions while simultaneously enforcing conventional commits and required Bruno API documentation for new endpoints.

How do I enforce LGPD compliance and architecture layer validation before merging a pull request?

Enforcing LGPD compliance and architecture layer validation is handled through automated pre-flight checks during PR creation. These checks validate testing requirements and governance rules, ensuring only compliant pull requests pass through the GitHub-based pipeline.

Does automated PR governance work with Bruno API documentation and audit-log requirements?

Automated PR governance works directly with Bruno API documentation and audit-log requirements by enforcing them through automated checks. When submitting a feature branch PR, the pipeline validates that new endpoints include required Bruno documentation and audit logs before approval.

Can I use automated PR management for Pequi and similar GitHub-based projects?

Automated PR management is designed for GitHub-based workflows for Pequi and similar projects. It applies governance checks, structured description generation, and compliance validation to ensure your project maintains consistent pull request standards across contributions.

Why do I need automated pre-flight checks for pull request eligibility?

Automated pre-flight checks for pull request eligibility prevent manual review errors and governance drift. They validate LGPD compliance, architecture layers, testing requirements, conventional commits, and Bruno documentation before a PR enters the review pipeline, reducing human error.