Add Cursor command for doc impact #4558
Draft
Conversation
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
github-actions
bot
added
Needs tech review
11 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
What changes are you introducing?
Adding a new Cursor command that should determine whether a code PR has documentation impact and also suggest changes to cover the impact.
Why are you introducing these changes? (Explanation, links to references, issues, etc.)
Efficiency.
Anything else to add? (Considerations, potential downsides, alternative solutions you have explored, etc.)
The command is based on an instruction for Cursor that I have used a few times in the past and it worked quite nicely. I'm currently testing a modified version of the original instruction as a Cursor command and will keep this PR as a draft until I've tried it enough times to see that it provides good results. I'm sharing it early like this in case anyone else would like to start testing it too and share feedback on their results.
Contributor checklists
Please cherry-pick my commits into: