Repository navigation
Add Cursor commands for commit and PR description generation - #826
Merged
Merged
Conversation
Introduced a new markdown file outlining the process for creating effective git commits. The guidelines emphasize the importance of clear, descriptive commit messages, the use of semantic commit types, and best practices for grouping related changes. This addition aims to enhance the consistency and quality of commit messages across the project.
Introduced a new markdown file that outlines the process for generating informative PR titles and descriptions. The guidelines include prerequisites for comparing branches, instructions for inspecting changes, and requirements for documenting database changes. This addition aims to streamline the PR creation process and improve clarity for reviewers.
Contributor
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 9 minutes. View limit detailsLimit details: You’ve used the included review currently available. Review configuration: ⚙️ Run configuration
📒 Files selected for processing (2)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
panosatkinde
changed the title
Deploying kinde-docs-preview with
|
| Latest commit: |
f99d876
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://5debcf0d.kinde-docs-preview.pages.dev |
| Branch Preview URL: | https://dev-workflow.kinde-docs-preview.pages.dev |
kindeshubham
approved these changes
Oct 9, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds two Cursor slash-command guides under
.cursor/commands/so agents follow a consistent process when creating commits and drafting pull requests.What's included
generate-commit.md<type>(<scope>): <short description>(feat,fix,refactor,style,docs,test,chore)main/master, no AI attribution / co-author lines, prefer signed commits, push after confirmationgenerate-pr-description.mdorigin/main: fetch, verify ancestry, merge only with user approvalMotivation
Standardize how Cursor agents create git commits and PR write-ups so reviewers get clearer history and PR descriptions, and so branch comparisons against
mainstay accurate (fresh fetch + merge checks before diffing).Database changes
None.
Test plan
.cursor/commands/and are picked up as Cursor commands/generate-commiton a sample change set and verify the agent asks for confirmation before committing, uses semantic messages, and omits attribution/generate-pr-descriptionon a feature branch and verify it fetchesorigin/main, checks merge ancestry, and writes Markdown to a system temp file (not the repotmp/)