Add Git workflow instructions to AGENTS.md

Include guidance on using conventional-commit and
git-advanced-workflows skills. Update the package addition example to
reference the conventional-commit skill instead of raw git commands.
This commit is contained in:
2026-05-06 11:03:30 +03:00
parent 69a34cb819
commit e2062a2248

View File

@@ -251,6 +251,28 @@ When modifying overlay behavior:
- [Nix Flake Patterns](https://github.com/NixOS/flake-patterns) - [Nix Flake Patterns](https://github.com/NixOS/flake-patterns)
- [Rust in Nixpkgs](https://nixos.org/manual/nixpkgs/stable/#rust) - [Rust in Nixpkgs](https://nixos.org/manual/nixpkgs/stable/#rust)
## Git Workflow
### Committing Completed Work
Every completed job or feature must be committed to the git repository.
When preparing git commits, always use the `conventional-commit` skill to create proper commit messages following conventional commit conventions.
This ensures:
- Clean git history with proper commit message formatting
- No work is left uncommitted
- Consistent commit message style across the project
### Advanced Git Operations
For advanced Git workflows (rebasing, cherry-picking, bisect, worktrees, reflog, history recovery), use the `git-advanced-workflows` skill.
This skill provides:
- Master advanced Git workflows including rebasing, cherry-picking, bisect, worktrees, and reflog
- Maintain clean history and recover from any situation
- Manage complex Git histories, collaborate on feature branches, or troubleshoot repository issues
## Example Workflow: Adding a New Package ## Example Workflow: Adding a New Package
```bash ```bash
@@ -272,7 +294,7 @@ nix build .#my-tool
# 6. Update README.md with new package info # 6. Update README.md with new package info
# 7. Commit changes # 7. Commit changes using conventional-commit skill
git add packages/my-tool README.md git add packages/my-tool README.md
git commit -m "Add my-tool package" # Then invoke: skill: "conventional-commit"
``` ```