pm-git-file-tracking

Enforces git add and commit for agent-created files before task completion.

Updated Jan 30, 2026
One-click install
npx skills add https://github.com/MacPhobos/research-mind --skill pm-git-file-tracking
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pm-git-file-tracking
Source: https://github.com/MacPhobos/research-mind/tree/main/.claude/skills/mpm-git-file-tracking
Command: npx skills add https://github.com/MacPhobos/research-mind --skill pm-git-file-tracking

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents the loss of agent-created files by mandating immediate Git tracking before a task is marked as complete, ensuring all deliverables are version-controlled.

Core Features & Use Cases

  • Immediate File Tracking: Enforces git add and git commit for new deliverables right after agent creation.
  • Decision Matrix: Clearly defines which file types must be tracked and which can be ignored.
  • Use Case: After an agent writes new Python code, this skill ensures it's added to Git before the agent can proceed, preventing code from being lost.

Quick Start

Use the pm-git-file-tracking skill to add and commit any new Python files created by the agent.

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 ensure Git tracks files immediately after an agent creates them?

To ensure immediate Git file tracking, you can enforce automated git add and git commit operations directly after agent deliverables are created. This prevents task completion until all relevant new files are version-controlled and committed.

What types of files need to be committed to version control automatically?

Source code, configuration files, documentation, and test files require immediate Git tracking. A decision matrix clearly defines which deliverables must be committed versus which file types can be safely ignored.

How do I automate git add and git commit for new source code?

Automating git add and git commit involves running git status to identify changes, staging the deliverables, and executing a commit with a specified message format to prevent untracked code loss.

Do I need an existing Git repository to enforce immediate file tracking?

Yes, immediate file tracking requires an existing Git repository to execute git status, git add, and git commit commands, ensuring new agent-created deliverables are properly version-controlled.

What's the best way to prevent agent-created files from being lost?

The best way to prevent file loss is mandating immediate Git tracking before a task is marked complete, ensuring all deliverables are explicitly added and committed to version control.

Why does my workflow allow task completion without committing new files?

Workflows lack immediate file tracking enforcement, allowing task completion without Git commits. Enforcing a mandatory git add and git commit step prevents untracked deliverables and ensures version control.