git-protocol
Skill0 starsChanged 3 months agoMITView on GitHub
Audit git workflow compliance including branch architecture, commit standards, issue linkage, and production readiness (check git compliance, audit branches, git hygiene).
- Reads credentials
1 other project uses a version of this.
Adopted by
Most recently taken up by
- ReaperOAK/ForgeOStheir own version, first seen Jun 8, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- ReaperOAK/ForgeOS★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository44 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- a11y-auditSkill
- ai-engineerSkill
- api-clientSkill
- changelog-enforcerSkill
- code-cleanup-guardianSkill
- code-reviewerSkill
- contract-testSkill
- db-migrateSkill
- dep-auditSkill
- devops-automatorSkill
- env-configSkill
- error-observabilitySkill
- frontend-designSkill
- git-commit-helperSkill
- github-issues-managerSkill
- git-issue-syncSkill
- handoffSkill
- incident-responseSkill
- init-projectSkill
- karpathy-guidelinesSkill
- market-researcherSkill
- parallel-agent-git-isolationSkill
- product-strategistSkill
- pr-workflowSkill
- rapid-builderSkill
- release-managerSkill
- resumeSkill
- scrutinizeSkill
- shadcn-uiSkill
- skill-builderSkill
- sprint-plannerSkill
- state-machine-diagramsSkill
- state-managementSkill
- surveySkill
- system-architectSkill
- tech-docsSkill
- unstuckSkill
- ux-design-systemSkill
- ux-researchSkill
- webapp-testingSkill
- web-dev-fundamentalsSkill
- workflow-optimizerSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 39
Verify main and prod branches exist
- Very specific: line 44
Check each of the last 20 commits against conventional format: type(scope): description
- Distinctive: line 50
Check for orphaned issues (no linked commits)
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Git Protocol Enforcement
Audit scope: $ARGUMENTS (blank = full audit)
Pre-fetched State
All Branches
!git branch -a 2>/dev/null || echo "Not a git repository"
Current Branch
!git branch --show-current 2>/dev/null
Last 20 Commits
!git log --oneline -20 2>/dev/null
Open Issues
!gh issue list --state open --limit 20 --json number,title,labels 2>/dev/null | jq -r '.[] | "#\(.number): \(.title)"' 2>/dev/null || echo "No GitHub CLI or repo"
Tracked .env Files
!git ls-files 2>/dev/null | grep -E "\.env" || echo "None tracked"
Your Task
Using the pre-fetched data above, run a comprehensive audit:
Phase 1: Branch Architecture
- Verify
mainandprodbranches exist - Validate all branch names follow
feature/*orhotfix/*convention - Flag non-standard names
Phase 2: Commit Standards
- Check each of the last 20 commits against conventional format:
type(scope): description - Valid types: feat, fix, docs, style, refactor, perf, test, chore, build, ci, revert
- Flag commits without issue references (#N)
Phase 3: Issue Linkage
- Identify commits without issue references
- Check for orphaned issues (no linked commits)
Phase 4: Production Readiness
Scan for violations:
grep -rn --include="*.ts" --include="*.tsx" --include="*.js" --include="*.jsx" --include="*.py" --include="*.go" --include="*.rs" \
-E "console\.(log|debug|info|warn|error)|debugger" src/ 2>/dev/null || echo "None found"
grep -rn --include="*.ts" --include="*.tsx" --include="*.js" --include="*.jsx" --include="*.py" --include="*.go" --include="*.rs" \
-E "(TODO|FIXME|HACK|XXX):" src/ 2>/dev/null || echo "None found"
# Not violations on their own: list colocated tests so you can confirm the build excludes them
find src/ \( -name "*.test.*" -o -name "*.spec.*" \) 2>/dev/nullPhase 5: Branch Hygiene
- Stale branches (14+ days no activity)
- Merged branches that can be deleted
- Branches without upstream tracking
Generate Compliance Report
| Area | Check | Status |
| Branches | Core branches exist | OK/FAIL |
| Branches | Naming convention | X violations |
| Commits | Conventional format | X/20 compliant |
| Commits | Issue references | X/20 linked |
| Issues | Open count | X |
| Prod | Debug statements | X found |
| Prod | TODO comments | X found |
| Hygiene | Stale branches | X |
| Hygiene | Merged (deletable) | X |
Overall compliance: X%
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

