skills.rest
Ryokuman
RyokumanCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

main-v3-pr-scope-gate

Validates branch names and diff scope before creating tier-0 pull requests.

1|Updated Jul 3, 2026
Search Tags:#git#code review#pull request#governance#monorepo#branch naming#scope validation
One-click install
npx skills add https://github.com/Ryokuman/new_human_ochestrator --skill main-v3-pr-scope-gate-ryokuman
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: main-v3-pr-scope-gate
Source: https://github.com/Ryokuman/new_human_ochestrator/tree/main/system/20-skills/main-v3-pr-scope-gate
Command: npx skills add https://github.com/Ryokuman/new_human_ochestrator --skill main-v3-pr-scope-gate-ryokuman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It prevents project-specific SSoT files, silo-local artifacts, and mixed-scope changes from leaking into tier-0 common-rule pull requests targeting main-v3/main. ## Core Features & Use Cases - Diff Classification: Categorizes changed files into tier-0 common changes, tier-1 project SSoT, tier-2 Project Work SSoT, and tier-3 local/silo artifacts using git diff against the base branch. - Branch Name Validation: Checks that work branches follow the main-v3/{taskname} or project-{projectName}/{taskname} naming model before push or PR creation. - Block and Allow Rules: Stops PR proposal when project SSoT originals, silo data, or mixed tier changes appear, and permits only commonizable rule, template, and config changes. - Use Case: Before running gh pr create against main-v3/main, run this gate to confirm the diff contains only system/ or AGENTS.md changes and receive a structured go/no-go report. ## Quick Start Ask the agent to check whether the current branch diff is eligible for a main-v3/main PR before creating the pull request.

Frequently Asked Questions about main-v3-pr-scope-gate

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

FAQPage Schema
How do I check if my branch is ready for a main-v3/main PR?▼

Fetch origin main-v3/main, then run git diff --name-only and --stat against it. Classify each changed file into tier-0 common changes or project/silo content; only pure tier-0 diffs are eligible for the PR.

What branch naming convention does this gate enforce?▼

Tier-0 work branches must follow main-v3/{taskname}, and project work branches must follow project-{projectName}/{taskname}. Legacy compatible forms like project-{projectName}-{taskname} or project/<project-id> are recognized but not the target model.

What changes are blocked from a main-v3/main pull request?▼

PRs are blocked when the diff contains project SSoT originals, Project Work SSoT files, silo-local artifacts, mixed tier-0 and project changes, or unexplained promotion candidates. Docs/chore branches containing only project data are also blocked.

Can I mix system rule changes and project SSoT updates in one PR?▼

No. Mixed changes must be split: the tier-0 system changes go into a main-v3/{taskname} worktree and PR, while project SSoT updates go into a project-{projectName}/{taskname} branch targeting the project main branch.

When should project findings be promoted to common rules?▼

Promotion is appropriate only when the change is a reusable rule, template, or config example applicable across projects, such as setup.sh scaffold logic. The promotion candidate must be explicitly explained before proposing a tier-0 PR.

Related Skills

Explore More Software Engineering Skills→
mvillmowmvillmow
18

worktree-sync

Syncs Git worktrees by fetching remote and rebasing or merging main into feature branches.

Community
Basic
zuzu59zuzu59

create-pr

Generate pull request titles and bodies from local changes via GitHub CLI.

Community
Advanced
streamlitstreamlit
45.7k

finalizing-pr

Automates branch finalization with checks, code review, and pull request creation.

Official
Advanced
kittnekittne

github

Enforce GitHub branch protections, CODEOWNERS reviews, and dependency scans across repositories.

Community
Advanced