Ruleset Governance
Design, review, and apply lightweight GitHub rulesets for branch and tag protection, required checks, signed commits, force-push blocking, file restrictions, and single-developer bypass policy. Use when asked to harden merge rules, protect main, or standardize rulesets across repositories.
Install
$ agentstack add skill-ravisingh11-agent-safe-engineering-ruleset-governance ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-ravisingh11-agent-safe-engineering-ruleset-governance) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Ruleset Governance
Use this skill for GitHub branch, tag, and push ruleset design.
Workflow
- Inspect current branch protection, rulesets, default branch, required checks, bypass actors, and repository risk tier.
- Choose the lightest rule that protects the repo without slowing solo development.
- Prefer evaluate or warn-first rollout for broad org changes unless the user explicitly asks for enforcement.
- Apply strict rules only where checks are stable and recovery paths are clear.
- Re-read ruleset state after changes.
Recommended Solo-Developer Baseline
- Block force pushes and branch deletion on
main. - Require status checks only when validation is stable and available to the repository.
- Allow owner/admin bypass for emergency recovery.
- Do not require pull requests or PR reviews for single-developer repositories.
- Consider mandatory PR review only when a repo has external contributors or production-critical deploy gates.
- Do not require checks from a CI system that the repository has not adopted.
Decision Rules
- Do not require signed commits org-wide without confirming the user's signing setup.
- Do not require a check that is flaky, missing, or named inconsistently.
- Do not require runner-backed checks if the repo does not have reliable runner capacity.
- Do not apply release/tag restrictions to repos that do not publish releases.
- Keep ruleset names explicit:
main-safety,release-tags,push-hygiene.
References
- GitHub ruleset rule types:
references/ruleset-baseline.md
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: ravisingh11
- Source: ravisingh11/agent-safe-engineering
- License: Apache-2.0
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.