Add Cursor command for doc impact#4558
Add Cursor command for doc impact#4558aneta-petrova wants to merge 1 commit intotheforeman:masterfrom
Conversation
github-actions
bot
added
Needs tech review
|
Works quite nicely. Also, please, rebase so that the diff is accurate. |
Thanks for giving it a try! I think that rather than recording repo-specific rules in this command file (and by extension every other command and skill file), it would be best if we recorded these rules somewhere where Cursor/Claude/anything else reads it every time they make a change. So yes, let's look into that -- not in this PR but perhaps something like a separate skill file that loads the readme, contribution guidelines, etc.? We should totally explore that later.
👍 |
|
2 suggestions:
|
|
After further discussion downstream, the preference is to use downstream tools that also involve the JIRA instance available there. Closing. |
2 participants
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: