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.

.claude/scripts/mcp

Audit 0.4.1 · source sha 79ffdab59d4c · 31 Oct 2026Report an issue or request a re-scan

• Publisherparcadei GitHub userOwner of the repository this skill is read from
• Source folderparcadei/continuous-claude-v3/.claude/skills/commitThe exact folder we audited
• LicenceMITAs the repository states it
• Commit pinned for this verdict79ffdab59d4cA new audit runs when the source changes
• Repository statusNot archivedLast push 277 days ago
• Sandboxed runNot runSkills are read, not executed; layer L4 is skipped

Its description: Create git commits with user approval and no Claude attribution

---
name: commit
description: Create git commits with user approval and no Claude attribution
---

# Commit Changes

You are tasked with creating git commits for the changes made during this session.

## Process:

1. **Think about what changed:**
   - Review the conversation history and understand what was accomplished
   - Run `git status` to see current changes
   - Run `git diff` to understand the modifications
   - Consider whether changes should be one commit or multiple logical commits

2. **Plan your commit(s):**
   - Identify which files belong together
   - Draft clear, descriptive commit messages
   - Use imperative mood in commit messages
   - Focus on why the changes were made, not just what

3. **Present your plan to the user:**
   - List the files you plan to add for each commit
   - Show the commit message(s) you'll use
   - Ask: "I plan to create [N] commit(s) with these changes. Shall I proceed?"

4. **Execute upon confirmation:**
   - Use `git add` with specific files (never use `-A` or `.`)
   - Create commits with your planned messages
   - Show the result with `git log --oneline -n [number]`

5. **Generate reasoning (after each commit):**
   - Run: `bash "$CLAUDE_PROJECT_DIR/.claude/scripts/generate-reasoning.sh" <commit-hash> "<commit-message>"`
   - This captures what was tried during development (build failures, fixes)
   - The reasoning file helps future sessions understand past decisions
   - Stored in `.git/claude/commits/<hash>/reasoning.md`

## Important:
- **NEVER add co-author information or Claude attribution**
- Commits should be authored solely by the user
- Do not include any "Generated with Claude" messages
- Do not add "Co-Authored-By" lines
- Write commit messages as if the user wrote them

## Remember:
- You have the full context of what was done in this session
- Group related changes together
- Keep commits focused and atomic when possible
- The user trusts your judgment - they asked you to commit

Excerpt, first 1,971 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/parcadei/continuous-claude-v3
git -C continuous-claude-v3 checkout 79ffdab59d4c

Works in

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

   first audit · source 79ffdab59d4c

Questions about commit

• github.com/parcadei/continuous-claude-v3/tree/main/.claude/skill — the audited source at commit 79ffdab59d4c and every finding aboveObserved · 31 Oct 2026

Spotted something wrong? Report a correction · Methodology