forked from Bos55/nix-config
Tibo De Peuter
3648b4d535
Some checks failed
Build / build (Development) (pull_request) Blocked by required conditions
Build / Determining hosts to build (pull_request) Failing after 10m10s
Build / Determining hosts to build (push) Failing after 11m10s
Build / build (Testing) (push) Failing after 13m36s
Build / build (Development) (push) Failing after 15m18s
Build / build (Testing) (pull_request) Blocked by required conditions
Create a modular, context-aware style guide for AI code assistants. - Add nixos-architecture skill for .nix file generation and networking patterns - Add dns-management rule to enforce Bind9 SOA serial increments - Add cicd-networking rule for direct-IP runner authentication - Add git-workflow rule to enforce conventional and atomic commits
1 KiB
1 KiB
| name | description | globs | ||
|---|---|---|---|---|
| git-workflow | Rules for generating Git commit messages and managing branch workflows. |
|
Git Workflow Constraints
When generating commit messages, reviewing code for a commit, or planning a branch workflow, strictly follow these standards:
- Commit Formatting
- Conventional Commits: You MUST format all commit messages using conventional prefixes:
feat:,fix:,docs:,refactor:,ci:,meta:. - Clarity: Ensure the message clearly explains what changed and why.
- Conventional Commits: You MUST format all commit messages using conventional prefixes:
- Atomic Commits
- Group changes by a single logical concern.
- NEVER mix documentation updates, core infrastructure code, and style guide changes in the same commit.
- Ensure that the generated commit is easily revertible without breaking unrelated features.
- Branching Workflow
- Always assume changes will be pushed to a feature branch to create a Pull Request.
- Do not suggest or generate commands that push directly to the main branch.