repo-config

Configure branch protection, required checks, secrets, and deploy hooks for merge gates.

9|2|Updated Jun 6, 2026
One-click install
npx skills add https://github.com/app-vitals/shipwright --skill repo-config-app-vitals
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: repo-config
Source: https://github.com/app-vitals/shipwright/tree/main/plugins/shipwright/skills/repo-config
Command: npx skills add https://github.com/app-vitals/shipwright --skill repo-config-app-vitals

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill defines the repository-level controls that make “tests pass” meaningful, so CI is not just advisory and risky changes cannot slip through on an unprotected main branch.

Core Features & Use Cases

  • Branch Protection: Specify required PR reviews, required status checks, up-to-date merges, and admin enforcement.
  • Secrets & Environments: Map external integrations to GitHub secrets and deployment targets to GitHub environments.
  • Deploy, Canary, and Promote Wiring: Ensure staging deploys, canary validation, and production promotion are connected with the correct success checks and target URLs.
  • PR Conventions: Standardize closing references, verification output, and acceptance-criteria checklists in pull requests.
  • Use Case: A team preparing a repository for reliable delivery uses this Skill to turn a loose CI setup into a governed release pipeline with explicit merge gates.

Quick Start

Use the repo-config skill to audit this repository’s branch protection, required checks, secrets, environments, deploy hooks, and pull request conventions for a test-ready delivery pipeline.

Frequently Asked Questions about repo-config

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

FAQPage Schema
How do I turn CI results into an enforceable merge gate on GitHub?

To turn CI results into a merge gate, you wire explicit required status checks into GitHub branch protection rules, ensuring CI success is mandatory before any pull request can merge into the main branch.

What's the best way to wire GitHub environments and secrets for a canary deployment pipeline?

Wire GitHub environments by mapping deployment targets to environment-scoped secrets, then connect staging deploys, canary validation, and production promotion using deploy-to-canary-promote result checks.

How does branch protection enforce pull request conventions for test-readiness pipelines?

Branch protection enforces test-readiness by requiring up-to-date merges, explicit status checks, and standardized PR conventions including verification output and acceptance-criteria checklists before allowing a merge.

Do I need required status checks for staging deploys and canary promotion?

Yes, required status checks are necessary to connect staging deploys, canary validation, and production promotion, ensuring each deployment phase validates successfully before the next promotion step occurs.

Why does CI pass but changes still merge to an unprotected main branch?

CI passes but changes merge because branch protection lacks explicit required status check wiring and admin enforcement, making the CI setup advisory rather than a governed release pipeline with real merge gates.