Git Commit

What the source does

• FilesystemNone observedNo reads or writes in the source
• NetworkNone observedNo outbound calls in the source
• ShellNone observedNo commands run in the source
• DependenciesPinnedNothing floats
• SecretsNone foundNo keys in source

Five audit layers

Gates applied: no behavioural pass, no license.

Audit 0.4.1 · source sha dd4da722e22a · 18 Oct 2026Report an issue or request a re-scan

• Publisheragulli GitHub userOwner of the repository this skill is read from
• Source folderagulli/atlas-agents/ch09_agent_skills/skills/git-commitThe exact folder we audited
• LicenceNot declaredAs the repository states it
• Commit pinned for this verdictdd4da722e22aA new audit runs when the source changes
• Repository statusNot archivedLast push 93 days ago
• Sandboxed runNot runSkills are read, not executed; layer L4 is skipped

Its description: Create well-structured git commits with conventional commit messages. Use when asked to commit changes, prepare a commit, or stage and push code.

---
name: git-commit
description: Create well-structured git commits with conventional commit messages. Use when asked to commit changes, prepare a commit, or stage and push code.
license: MIT
compatibility: Requires git
allowed-tools: Bash(git:*)
---

## Process

1. **Run `git status`** to see all changed files. Read the output carefully.
2. **Run `git diff --stat`** to understand the scope of the change.
3. **Group related changes.** If the diff contains unrelated changes (e.g., a bug fix AND a new feature), create separate commits. Do not bundle unrelated work.
4. **Stage files intentionally.** Use `git add <specific-files>`, never `git add .` unless every changed file belongs in the same logical commit.
5. **Write the commit message** using Conventional Commits format:
   ```
   <type>(<scope>): <description>

   <body — explain WHY, not WHAT>

   <footer — references, breaking changes>
   ```
   Types: `feat`, `fix`, `refactor`, `docs`, `test`, `chore`, `perf`, `ci`
6. **Verify before committing.** Run `git diff --cached` to review exactly what will be committed. Read the staged diff.
7. **Commit.** Run `git commit -m "..."` with the message.

## Rationalizations

| Excuse | Rebuttal |
|--------|----------|
| "I'll just use `git add .` to save time" | Staging everything blindly leads to committing debug files, env vars, and unrelated changes. Stage intentionally. |
| "The message 'fix stuff' is fine for now" | Every commit message is permanent history. Write it properly the first time. |
| "I'll squash these later" | You won't. Write clean commits now. |

## Verification

- [ ] `git diff --cached` output was reviewed before committing
- [ ] Commit message follows Conventional Commits format
- [ ] No unrelated changes were bundled into a single commit
- [ ] No `.env`, `__pycache__`, or build artifacts were staged

Excerpt, first 1,848 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.

git clone https://github.com/agulli/atlas-agents
git -C atlas-agents checkout dd4da722e22a

Works in

1. 2026-10-18
   ✓SAFE B 89 / 100

   first audit · source dd4da722e22a

Questions about Git Commit

• github.com/agulli/atlas-agents/tree/main/ch09_agent_skills/skill — the audited source at commit dd4da722e22a and every finding aboveObserved · 18 Oct 2026

Spotted something wrong? Report a correction · Methodology