create-pr

Orchestrate pre-pull request validation for the swiss-ai-hub monorepo.

9|2|Updated Nov 29, 2024
One-click install
npx skills add https://github.com/bbvch-ai/aihub-core --skill create-pr-bbvch-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-pr
Source: https://github.com/bbvch-ai/aihub-core/tree/main/.claude/skills/create-pr
Command: npx skills add https://github.com/bbvch-ai/aihub-core --skill create-pr-bbvch-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the risk of incomplete pre-pull request validation that causes merge conflicts, failing CI pipelines, and out-of-sync documentation across the swiss-ai-hub monorepo, reducing manual rework for developers.

Core Features & Use Cases

  • End-to-End Pre-PR Orchestration: Coordinates commit validation, main branch sync, linting, scoped testing, code review, and documentation updates in the correct order.
  • Scope-Aware Testing: Automatically detects affected monorepo scopes from git changes and runs tests for all dependent packages to catch integration issues early.
  • Use Case: A developer working on a new RAG pipeline feature can use this Skill to ensure all commits follow the required conventional format, tests pass for all affected and dependent scopes, code meets security and architecture standards, and related documentation is updated before opening a pull request.

Quick Start

Use the create-pr skill to validate all your recent changes for the swiss-ai-hub monorepo and prepare them for a pull request.

Frequently Asked Questions about create-pr

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

FAQPage Schema
How do I automate pre-pull request validation for a monorepo?

Pre-pull request validation for a monorepo is automated by orchestrating commit formatting, linting, scoped testing, and branch synchronization to prevent merge conflicts and failing CI pipelines.

How does scope-aware testing work for monorepo git workflows?

Scope-aware testing for monorepo git workflows detects affected scopes from recent changes and automatically runs test suites for all dependent packages to catch integration issues early.

What steps are required to prepare a pull request for feature development?

Preparing a pull request for feature development requires conventional commit formatting, passing scoped test suites, code review approval, main branch synchronization, and documentation consistency.

Does pre-merge linting check documentation consistency across all monorepo scopes?

Yes, pre-merge linting checks documentation consistency across all monorepo scopes, ensuring related docs are updated alongside code changes before pull request submission.

Why do my pull requests keep failing CI pipelines in a monorepo?

Pull requests fail CI pipelines in a monorepo due to incomplete pre-merge checks, unsynchronized branches, or missing tests for dependent scopes affected by your changes.