Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Git Rules

ASecurity

Git + repo discipline — git-workflow (per-org identity, conventional commits, PR workflow), repo-setup-checklist (20-point first-touch security audit), docs-sync-with-code (every PR ships docs + code together), documentation-requirements (Diátaxis four-quadrant: tutorials / how-tos / reference / explanation). Select explicitly when this guidance applies.

12 stars
0 votes
0 copies
0 views
Added 10/6/2026
ai-agentsgonodegitapisecuritydocumentation

Works with

api

Security Analysis

A100/100

Pro scans all 5 files and shows the line behind each finding

Scanned 10/6/2026

$npx -y skills add Nmor/the-council --skill git-rules --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Git Rules?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Git Rules
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/nmor-git-rules-the-council/badge)](https://www.skillsdirectory.com/skills/nmor-git-rules-the-council)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: git-rules
description: Git + repo discipline — git-workflow (per-org identity, conventional commits, PR workflow), repo-setup-checklist (20-point first-touch security audit), docs-sync-with-code (every PR ships docs + code together), documentation-requirements (Diátaxis four-quadrant: tutorials / how-tos / reference / explanation). Select explicitly when this guidance applies.
paths:
  - "**/.gitignore"
  - "**/.gitattributes"
  - ".git/**"
  - ".githooks/**"
  - "CONTRIBUTING.md"
  - "README.md"
  - "**/CONTRIBUTING.md"
  - "**/README.md"
  - "docs/**/*.md"
  - "**/docs/**/*.md"
disable-model-invocation: true
---

# git-rules

> **Size budget: 25 KB.** Check: wc -c. Gate: node ~/.claude/scripts/token-budget.mjs --check
>
> Migrated 2026-06-02 from `~/.claude/rules/common/` as part of the lazy-rules-loading plan. Phase H
> will delete the source files to close the eager-load loop.

## Purpose

Git and repo discipline: who a commit is authored as, what a repo must satisfy
before work starts in it, and the documentation that ships alongside the code.
This file is a ROUTING TABLE — the detail lives in `references/`, one file per
concern, read on demand rather than carried on every turn that touches a
`README.md` or a `docs/` page.

## Routing table

| Row | Read when | Reference file |
| --- | --- | --- |
| **Git workflow** | Committing, branching, opening a PR, or first-touching a repo in a different GitHub org (per-org identity + signing keys) | [`references/git-workflow.md`](references/git-workflow.md) |
| **Repo setup checklist** | A repo is cloned, initialised, first-touched this session, or last touched > 30 days ago — the 20-point tracked-state / dependency / infra / secrets / CI audit | [`references/repo-setup-checklist.md`](references/repo-setup-checklist.md) |
| **Docs sync with code** | A change alters user-visible behaviour, or a stale doc / landing page is encountered while working on something else | [`references/docs-sync-with-code.md`](references/docs-sync-with-code.md) |
| **Documentation requirements** | Authoring or reviewing any doc surface — README, architecture, ADR, runbook, API reference, tutorials — or choosing a doc toolchain | [`references/documentation-requirements.md`](references/documentation-requirements.md) |

## Source files migrated

- `rules-library/common/git-workflow.md`
- `rules-library/common/repo-setup-checklist.md`
- `rules-library/common/docs-sync-with-code.md`
- `rules-library/common/documentation-requirements.md`

Attribution

NmorNmor
View sourceSee grades on GitHubMore from Nmor →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".

1100021 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

698461 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3421 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

741 votes
View all in ai-agents →