skills.rest
bobmatnyc
bobmatnycCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

pm-git-file-tracking

Track new deliverable files with git status, add, and commit.

Updated Mar 25, 2026
Search Tags:#git#workflow#todo#version-control#commit-message#file-tracking
One-click install
npx skills add https://github.com/bobmatnyc/claude-mpm-marketplace --skill pm-git-file-tracking-bobmatnyc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pm-git-file-tracking
Source: https://github.com/bobmatnyc/claude-mpm-marketplace/tree/main/plugins/claude-mpm/skills/mpm-git-file-tracking
Command: npx skills add https://github.com/bobmatnyc/claude-mpm-marketplace --skill pm-git-file-tracking-bobmatnyc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Delays and risk of lost deliverables occur when agents create files but tracking happens only at session end. This protocol ensures immediate tracking of new files to preserve version history and provide traceability.

Core Features & Use Cases

  • Blocking file-tracking workflow: after an agent creates files, PM runs the tracking steps (git status, add, commit) before closing the task.
  • Supports common file types: new source files, new config files, and new documentation.
  • Verification: after tracking, the working tree should be clean and the todo can be marked complete.

Quick Start

Immediately implement the file tracking protocol after an agent creates new files by running git status, adding the new files, and committing with a descriptive message.

Frequently Asked Questions about pm-git-file-tracking

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I track new files in git immediately after creation?▼

Immediate file tracking requires running git status, git add, and git commit with a descriptive message right after an agent creates new files. This blocking workflow preserves version history and prevents lost deliverables.

Why does my agent lose deliverables before the session ends?▼

Deliverables get lost when file tracking is delayed until session end. Implementing an immediate git commit workflow after file creation ensures new source, config, and documentation files are preserved in version control.

What's the best way to automate git commit messages for new deliverables?▼

The best way is a blocking workflow that enforces git status, git add, and git commit with contextual messages before a todo is marked complete. This ensures traceability for new source, config, and documentation files.

Does this file tracking workflow support config and documentation files?▼

Yes, this file tracking workflow supports new source files, config files, and documentation. It requires running git add and git commit for each before closing the task.

How do I verify a clean working tree after committing new files?▼

You verify a clean working tree by running a post-tracking verification step. Once confirmed clean, the associated todo can be safely marked complete.

Related Skills

Explore More Product & Management Skills→
mikersaysmikersays

issue-init

Initialize a structured issue tracking system in a Git repository.

Community
Intermediate
MartinoPoloMartinoPolo
1

mp-release

Bump npm versions, push tags, and verify GitHub Actions runs.

Community
Intermediate
AmidVoshakulAmidVoshakul

git-hooks-automation

Automate Git hook configuration for linting, formatting, and commit message validation.

Community
Advanced
a-taka-tak
1

git-commit-push

Automates staging, committing, and pushing with standardized Git workflow.

Community
Basic