qjudge-github-workflow-owner

Enforce branch, commit, PR, and release rules for GitHub repositories.

31|1|Updated Nov 30, 2025
One-click install
npx skills add https://github.com/quan0715/QJudge --skill qjudge-github-workflow-owner
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qjudge-github-workflow-owner
Source: https://github.com/quan0715/QJudge/tree/main/.codex/skills/qjudge-github-workflow-owner
Command: npx skills add https://github.com/quan0715/QJudge --skill qjudge-github-workflow-owner

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, gh, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Provides a single-owner policy and tooling to remove ambiguity around Git branching, commit practices, pull request creation, and dev-to-main releases so teams maintain consistent, reviewable changes and safe release gates.

Core Features & Use Cases

  • Branch and Release Rules: Defines permitted branch flows (codex/* -> dev, dev -> main) and forbids direct commits to main.
  • PR and Commit Guidance: Specifies PR size limits, required PR checklist items, label taxonomy, and commit/PR naming conventions.
  • Command-line Helpers: Includes scripts to standardize commits and to create PRs that validate branch context and push via git and the GitHub CLI.
  • Use Case: A contributor creates a codex/ feature branch, runs the provided commit script to stage and commit changes, runs linting gates, and uses the PR script to open a PR against dev with the required description and labels.

Quick Start

Run the commit script to stage and commit changes, then run the create-pr script to push and open a PR against dev or to prepare a dev->main release.

Frequently Asked Questions about qjudge-github-workflow-owner

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

FAQPage Schema
How do I enforce a git branching and release workflow for GitHub repositories?

To enforce a GitHub workflow, this skill defines permitted branch flows like codex/* to dev and dev to main, forbidding direct commits to main to maintain consistent, reviewable changes and safe release gates.

How do I standardize pull request creation and commit practices?

To standardize pull request creation, it specifies PR size limits, required checklist items, label taxonomy, and provides command-line helper scripts to validate branch context and push via git and the GitHub CLI.

Do I need the GitHub CLI to manage branch and release gates?

Yes, you need the GitHub CLI and git installed, as the command-line helpers invoke both tools to validate branch context, stage commits, push branches, and open pull requests against the dev branch.

What are the limitations for direct commits to main in a GitHub workflow?

Direct commits to main are forbidden to ensure safe release gates, requiring contributors to use codex/* feature branches into dev and subsequently prepare dev-to-main releases through validated pull requests.

Can I use this GitHub workflow policy for large pull requests?

No, this GitHub workflow policy enforces PR size limits to ensure reviewable changes, requiring contributors to break down large pull requests to meet the defined commit granularity and merge gate requirements.