From 9fd71126858ed4b35db185409c7a6637131b8437 Mon Sep 17 00:00:00 2001 From: cte Date: Thu, 8 Jan 2026 00:39:11 -0800 Subject: [PATCH] Add instructions to push --- .roo/commands/commit.md | 29 ++++++++++++++++++++++++++++- 1 file changed, 28 insertions(+), 1 deletion(-) diff --git a/.roo/commands/commit.md b/.roo/commands/commit.md index 64bc115854..7796c49fa9 100644 --- a/.roo/commands/commit.md +++ b/.roo/commands/commit.md @@ -1,5 +1,5 @@ --- -description: "Commit current changes with a descriptive message" +description: "Commit and push changes with a descriptive message" argument-hint: "[optional-context]" mode: code --- @@ -45,9 +45,36 @@ mode: code git commit -m "type(scope): brief description" ``` + **If pre-commit hooks fail:** + + - Review the error output (linter errors, type checking errors, etc.) + - Fix the identified issues in the affected files + - Re-stage the fixes: `git add -A` + - Retry the commit: `git commit -m "type(scope): brief description"` + +5. Push to the remote repository: + + ```bash + git push + ``` + + **If pre-push hooks fail:** + + - Review the error output (test failures, linter errors, etc.) + - Fix the identified issues in the affected files + - Stage and commit the fixes using steps 3-4 + - Retry the push: `git push` + **Tips for good commit messages:** - Keep the first line under 72 characters - Use imperative mood ("add", "fix", "update", not "added", "fixes", "updated") - Be specific but concise - If multiple unrelated changes exist, consider splitting into separate commits + +**Common hook failures and fixes:** + +- **Linter errors**: Run the project's linter (e.g., `npm run lint` or `pnpm lint`) to see all issues, then fix them +- **Type checking errors**: Run type checker (e.g., `npx tsc --noEmit`) to identify type issues +- **Test failures**: Run tests (e.g., `npm test` or `pnpm test`) to identify failing tests and fix them +- **Format issues**: Run formatter (e.g., `npm run format` or `pnpm format`) to auto-fix formatting