Planner Git Committer FAQs

Question 1

Does this skill push my code to a remote repository?

Accepted Answer

No, the Planner Commit skill only creates local commits. It never performs a git push, leaving that final step to the user for safety and manual review.

Question 2

How does it determine the commit scope?

Accepted Answer

The skill automatically derives the scope from the execution plan's filename. For example, 'auth-01-setup.md' results in an 'auth' scope. If the filename is ambiguous, it defaults to 'planner'.

Question 3

Can it fix commit errors automatically?

Accepted Answer

The skill handles errors gracefully by reporting failures to the user, ensuring you are notified if a commit cannot be completed due to merge conflicts or git configuration issues.

Question 4

What happens if I don't use the Conventional Commits standard?

Accepted Answer

If the auto_commit_standard is set to 'no_standard', the skill falls back to a simple, descriptive format: 'feat(planner): Complete [plan_name] - [summary]'.

Question 5

Does it handle multi-file changes differently?

Accepted Answer

Yes. If more than three files are modified, the skill automatically generates a multi-line commit message with a body that lists key changes and context for better documentation.

Planner Git Committer

Key Features

Use Cases

Planner Git Committer

Key Features

Use Cases