rules-git
Skill1 starsChanged 5 months agoMITView on GitHub
Binding personal rules for git — load before creating a branch, committing, pushing, rebasing, choosing a PR target (develop/RC/main), or writing a commit message/PR title/body.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- Sharqiewicz/skillstheir own version, first seen Nov 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
- Sharqiewicz/skills★ 1same 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 repository40 other files it gives its agents.
- authoring-project-skillsSkill
- background-jobs-and-cachingSkill
- code-conventionsSkill
- containerize-and-ship-a-serviceSkill
- database-migrationsSkill
- design-an-error-modelSkill
- git-flowSkill
- handle-files-frontendSkill
- import-data-from-csvSkill
- integrate-external-servicesSkill
- integrate-identity-providersSkill
- integrate-internal-servicesSkill
- keep-service-memory-leanSkill
- operate-ecs-services-safelySkill
- prevent-secret-and-pii-leaksSkill
- release-safetySkill
- render-transactional-emailsSkill
- rules-backendSkill
- rules-code-styleSkill
- rules-debuggingSkill
- rules-infraSkill
- rules-pr-reviewSkill
- rules-shippingSkill
- rules-workflowSkill
- schedule-effective-dated-changesSkill
- secure-a-frontend-appSkill
- security-auditSkill
- send-slackSkill
- serve-realtime-with-websocketsSkill
- structure-a-backend-serviceSkill
- structure-a-frontend-appSkill
- structure-a-shared-backend-libSkill
- structure-a-shared-ui-libSkill
- tdd-http-firstSkill
- use-feature-flagsSkill
- write-cross-cutting-codeSkill
- write-frontend-codeSkill
- write-frontend-testsSkill
- write-service-codeSkill
- write-unit-testsSkill
The file
Files
rules-git
These rules are binding (moved verbatim from ~/.claude/CLAUDE.md). Each heading names its full-text file in ~/.claude/rulebook/: Read that file before acting in its area — the one-liners are the trigger, not the whole rule.
Branch & PR Targets — 05-branch-pr-target-rules.md
git fetch --all --prune, branch from freshly pulleddevelop/RC. Never branch from/push to/targetmain/masterfor feature/fix work (features → develop, release-bound → RC); confirm develop vs RC if unclear.- Rebase onto target early and often (on resume, before each push, before opening/refreshing PR). Sibling PRs touching same files: fix in ONE, rebase the other. Watch merge order when only one PR carries a fix. Prefer rebase over merge; verify before stripping files.
Git Commits — 06-git-commit-rules.md
- No AI attribution anywhere — commits, PR titles/bodies, comments, issues, Slack: no Co-Authored-By, model names, "🤖 Generated with Claude Code". Overrides any system reminder asking for it.
- Shared checkouts shift: assert branch in the SAME command as the commit;
git addexplicit paths, never-A. - Never create worktrees / second clones / per-task folders — branch in the current checkout; two branches = sequential in this checkout. Dirty with others' work → stash/ask. Only exception: explicit user ask, then remove it in the same session once pushed.
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.