How do I install the Orbitant Git Hygiene skill?

Run npx skillmds@latest add weorbitant/orbitant-git-hygiene in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Orbitant Git Hygiene safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Orbitant Git Hygiene?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Orbitant Git Hygiene free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under MIT.

Who published Orbitant Git Hygiene?

weorbitant (@weorbitant) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Orbitant Git Hygiene by weorbitant — Agent Skill

Name: Orbitant Git Hygiene
Author: weorbitant

Orbitant Git Hygiene

Use when auditing git practices in a repo — Conventional Commits compliance, branch naming standards, secrets committed to history, direct commits to main, or stale branches. Activates when someone asks "is the git hygiene good here?", wants to check commit discipline, or needs to assess branch/release health before starting work on a project. Also trigger when someone asks "are my commits OK?", "is my branch name right?", or shares a git log — even if they don't explicitly mention "hygiene".

weorbitant 9f51f27 2 files · 5.2 KB Updated Sep 17, 2026

File contents

Overview

Audits git practices against Orbitant's engineering standards. Surfaces what's not following the standard — with file names, commit hashes, and branch names as evidence.

All checks are static. Derived from git history and tracked files.

When to Use

Checking if a project follows Conventional Commits
Auditing branch naming discipline
Scanning for committed secrets before a security review
Running a section audit after /orbitant-engineering:ground-control flagged git hygiene

How to Run

Load the reference standards:

@plugins/orbitant-engineering/skills/git-hygiene/references/git-hygiene.md

Key commands to run:

git ls-files | grep -E '\.env$'
git log --oneline -20
git branch -a

Collect all findings before printing the report.

Output Format

## Git Hygiene Audit   {rating}

### 🔴 Critical (fix first)
- .env file tracked in git
  File: config/.env
  Recommendation: remove from tracking, rotate any exposed secrets, add to .gitignore

### Passing
- .gitignore present and covers Node.js stack
- No direct commits to main in last 20 commits

### Failing
- Conventional Commits not enforced
  Finding: 4/20 commits compliant
  Examples: "fix stuff" (a3f1c2), "wip" (b9e2d1)
  Recommendation: add commitlint + husky commit-msg hook

Rating: ⚠️ Needs work

Ratings: ❌ Critical / ⚠️ Needs work / ✅ Compliant / 🚀 Strong hygiene

See references/git-hygiene.md for full scoring criteria and check details.

---name: orbitant-git-hygienedescription: Use when auditing git practices in a repo — Conventional Commits compliance, branch naming standards, secrets committed to history, direct commits to main, or stale branches. Activates when someone asks "is the git hygiene good here?", wants to check commit discipline, or needs to assess branch/release health before starting work on a project. Also trigger when someone asks "are my commits OK?", "is my branch name right?", or shares a git log — even if they don't explicitly mention "hygiene".license: MIT---## OverviewAudits git practices against Orbitant's engineering standards. Surfaces what's not following the standard — with file names, commit hashes, and branch names as evidence.All checks are static. Derived from git history and tracked files.---## When to Use- Checking if a project follows Conventional Commits- Auditing branch naming discipline- Scanning for committed secrets before a security review- Running a section audit after `/orbitant-engineering:ground-control` flagged git hygiene---## How to RunLoad the reference standards:`@plugins/orbitant-engineering/skills/git-hygiene/references/git-hygiene.md`Key commands to run:```bashgit ls-files | grep -E '\.env$'git log --oneline -20git branch -a```Collect all findings before printing the report.---## Output Format```## Git Hygiene Audit {rating}### 🔴 Critical (fix first)- .env file tracked in git File: config/.env Recommendation: remove from tracking, rotate any exposed secrets, add to .gitignore### Passing- .gitignore present and covers Node.js stack- No direct commits to main in last 20 commits### Failing- Conventional Commits not enforced Finding: 4/20 commits compliant Examples: "fix stuff" (a3f1c2), "wip" (b9e2d1) Recommendation: add commitlint + husky commit-msg hookRating: ⚠️ Needs work```Ratings: ❌ Critical / ⚠️ Needs work / ✅ Compliant / 🚀 Strong hygieneSee `references/git-hygiene.md` for full scoring criteria and check details.

Frequently asked questions