
Pm Git File Tracking
- 1 installs
- Updated May 18, 2026
- bobmatnyc/claude-mpm-marketplace
PM Git File Tracking is a Claude Code skill that defines a protocol for git-tracking and committing agent-created files immediately after creation, before a todo is marked complete.
About
PM Git File Tracking is a Claude skill defining a protocol for versioning files immediately after an agent creates them. It provides a decision flow, a track-vs-skip decision matrix, and a commit-message format so deliverables are committed before a todo is marked complete. Developers use it in a PM/agent orchestration flow to avoid losing new source, config, test, and script files between agent completion and session end.
- Protocol to git-add and commit agent-created files immediately, not at session end
- Decision matrix for which file types to track vs skip (source/tests vs tmp/build/deps)
- Blocking rule: a PM cannot mark a todo complete until deliverable files are tracked
Pm Git File Tracking by the numbers
- 1 all-time installs (skills.sh)
- Ranked #527 of 733 Git & Pull Requests skills by installs in the Skillselion catalog
- Data as of Jul 28, 2026 (Skillselion catalog sync)
pm-git-file-tracking capabilities & compatibility
- Capabilities
- git · file tracking · commit
- Use cases
- project management
What pm-git-file-tracking says it does
Protocol for tracking files immediately after agent creation
**BLOCKING REQUIREMENT**: PM cannot mark todo complete until files are tracked.
**Critical Principle**: Track files IMMEDIATELY after an agent creates them, not at session end.
npx skills add https://github.com/bobmatnyc/claude-mpm-marketplace --skill pm-git-file-trackingAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 1 |
|---|---|
| Last updated | May 18, 2026 |
| Repository | bobmatnyc/claude-mpm-marketplace ↗ |
What it does
Immediately git-add and commit agent-created deliverable files, gating todo completion until tracking is verified.
Who is it for?
PM/agent orchestration flows that must not lose deliverable files between agent completion and session end.
Skip if: Tracking temp files, build artifacts, dependencies, or non-core root markdown.
When should I use this skill?
An agent has just created files, before marking a todo complete or ending a session.
What you get
All deliverable files are committed immediately with a proper message and a clean working tree.
By the numbers
- 10-row track-vs-skip decision matrix
Files
Git File Tracking Protocol
Critical Principle: Track files IMMEDIATELY after an agent creates them, not at session end.
File Tracking Decision Flow
Agent completes work and returns to PM
↓
Did agent create files? → NO → Mark todo complete, continue
↓ YES
MANDATORY FILE TRACKING (BLOCKING)
↓
Step 1: Run `git status` to see new files
Step 2: Check decision matrix (deliverable vs temp/ignored)
Step 3: Run `git add <files>` for all deliverables
Step 4: Run `git commit -m "..."` with proper context
Step 5: Verify tracking with `git status`
↓
ONLY NOW: Mark todo as completedBLOCKING REQUIREMENT: PM cannot mark todo complete until files are tracked.
Decision Matrix: When to Track Files
| File Type | Track? | Reason |
|---|---|---|
New source files (.py, .js, etc.) | ✅ YES | Production code must be versioned |
New config files (.json, .yaml, etc.) | ✅ YES | Configuration changes must be tracked |
New documentation (.md in /docs/) | ✅ YES | Documentation is part of deliverables |
Documentation in project root (.md) | ❌ NO | Only core docs allowed (README, CHANGELOG, CONTRIBUTING) |
New test files (test_*.py, *.test.js) | ✅ YES | Tests are critical artifacts |
New scripts (.sh, .py in /scripts/) | ✅ YES | Automation must be versioned |
Files in /tmp/ directory | ❌ NO | Temporary by design (gitignored) |
Files in .gitignore | ❌ NO | Intentionally excluded |
Build artifacts (dist/, build/) | ❌ NO | Generated, not source |
Virtual environments (venv/, node_modules/) | ❌ NO | Dependencies, not source |
Commit Message Format
git commit -m "feat: add {description}
- Created {file_type} for {purpose}
- Includes {key_features}
- Part of {initiative}
🤖 Generated with [Claude MPM](https://github.com/bobmatnyc/claude-mpm)
Co-Authored-By: Claude MPM <https://github.com/bobmatnyc/claude-mpm>"Before Ending Any Session
Final verification checklist:
# 1. Check for untracked files
git status
# 2. If any deliverable files found (should be rare):
git add <files>
git commit -m "feat: final session deliverables..."
# 3. Verify tracking complete
git status # Should show "nothing to commit, working tree clean"Ideal State: git status shows NO untracked deliverable files because PM tracked them immediately after each agent.
Example Workflow
# After Engineer creates new OAuth files
git status
# Shows: src/auth/oauth2.js (untracked)
# src/routes/auth.js (untracked)
git add src/auth/oauth2.js src/routes/auth.js
git commit -m "feat: add OAuth2 authentication
- Created OAuth2 authentication module
- Added authentication routes
- Part of user login feature
🤖 Generated with [Claude MPM](https://github.com/bobmatnyc/claude-mpm)
Co-Authored-By: Claude MPM <https://github.com/bobmatnyc/claude-mpm>"
# Verify tracking complete
git status # Should show clean working treeIntegration with Todo Workflow
BLOCKING SEQUENCE: 1. Agent completes task and returns to PM 2. PM checks if files were created 3. If YES → Run file tracking protocol (cannot proceed until complete) 4. Only after tracking verified → Mark todo as completed
This ensures no deliverables are lost between agent completion and session end.