claude-code - 💡(How to fix) Fix [BUG] /commit-commands:commit doesn't work when there are no commits yet [1 comments, 2 participants]

⎿ Error: Shell command failed for pattern "!git log --oneline -10": [stderr]

Error Messages/Logs

TL;DR

The issue can be fixed by modifying the commit command to handle the case where there are no commits yet, potentially by adding a check for an empty commit history before running the git log command.

Guidance

• The error occurs because the git log command fails when there are no commits in the repository, so a check for this condition should be added to the commit command.
• To verify the issue, create a new repository with git init, install the commit-commands plugin, and run /commit-commands:commit to see if the error occurs.
• The commit command should be modified to handle the case where there are no commits yet, possibly by creating an initial commit if none exist.
• The git log command can be replaced with a command that checks if the repository has any commits, such as git rev-parse --is-inside-work-tree or git rev-list --count HEAD.

Example

No code example is provided as the issue does not specify the exact code that needs to be modified.

Notes

The issue may not be a regression, but rather a missing feature in the commit-commands plugin. The fix may require modifying the plugin to handle the case where there are no commits yet.

Recommendation

Apply workaround: The recommended solution is to modify the commit command to handle the case where there are no commits yet, as this is a specific and targeted fix for the issue at hand.