Automate git commits with change reasons for agent directories.
npx skills add https://github.com/typeclaw/typeclaw --skill typeclaw-git
Please help me install this Agent Skill. Skill: typeclaw-git Source: https://github.com/typeclaw/typeclaw/tree/main/src/skills/typeclaw-git Command: npx skills add https://github.com/typeclaw/typeclaw --skill typeclaw-git
This Skill helps maintain a clear, precise history of changes within your agent folder by enforcing disciplined commit habits tied to specific change reasons.
After editing a tracked file, invoke the commit command with an explanation of why the change was made.
High-intent search queries and answers about installing and using this skill.
You can automate git commits with reasons by invoking the commit command after editing tracked files, which requires you to provide a detailed explanation of the decision context to maintain an understandable change history.
The best way to maintain a clear history of agent directories is to enforce disciplined git commits immediately after file edits, ensuring structured tracking of modifications with specific change reasons recorded in each commit message.
Yes, you must provide decision context when committing changes to version control, as this preserves the reasoning behind modifications and supports effective auditing practices within your agent folder.
You can use automated change management to track configuration updates by prompting a commit with a detailed explanation immediately after you edit your agent's configuration or scripts.
You need to invoke the commit command for modified files immediately after editing a tracked file, providing an explanation of why the change was made to ensure every modification is recorded.
Yes, the automated commit process works without external dependencies, relying solely on internal scripts and references to enforce structured tracking of modifications within your agent directories.
chaimtInitialize a Git repository with an initial commit in the current directory.
jsalioDocument code changes with rationale in markdown files.
MCERQUAManage tenant file edits with Git version control and host coordination.
imMamdouhaboammarStage and commit changes with Conventional Commits format.
