Github ruleset architecture

Skill chf3198/megingjord-harness/skills/github-ruleset-architecture

Design and audit repository and organization ruleset architecture, including layering, bypass controls, enforcement modes, and merge queue compatibility.From its SKILL.md

Install

npx -y skills add chf3198/megingjord-harness --skill github-ruleset-architecture

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.0 KB, 382 tokens by cl100k_base, as published. Nobody here has run it

GitHub Ruleset Architecture

Purpose

Create a deterministic, auditable protection model using GitHub rulesets as primary governance controls.

Scope

Branch/tag rulesets
Push rulesets where supported
Ruleset layering with existing branch protection
Bypass actor minimization
Merge queue compatibility checks

Hard constraints

No destructive migration in one pass.
Preserve current enforcement unless explicitly approved.
Prefer staged rollout: Disabled -> validate -> Active.
Always report bypass principals explicitly.

Core checks

Ruleset target patterns (fnmatch) are precise and non-overlapping where possible.
Layered rules produce intended effective policy (most restrictive wins).
Bypass is least-privilege (role/team/app, justified).
Merge queue requirements align with rules/protections.
Required checks include merge_group readiness where merge queue is used.

Output contract

RULESET_ARCHITECTURE_REPORT
mode: <audit|design|migrate|verify>
scope: <repo|org>
policy_profile: <strict|standard|light>

current_state:
- rulesets_found: <count>
- branch_protection_found: <yes|no>
- merge_queue_required: <yes|no>

findings:
- id: R1
  result: <pass|fail|partial>
  observation: <what exists>
  risk: <low|medium|high>

proposed_changes:
1) change: <specific rule/ruleset>
   rationale: <why>
   rollout: <disabled-validate-active|direct>
   verification: <objective check>

decision:
- <apply|defer|NO_CHANGE>

missing_evidence:
- <none or required artifacts>

Invocation policy

Use before pre-merge governance hardening and before introducing merge queue/ruleset changes across repos.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.