📝 docs: automatically labeling Cursor-assisted PRs

[azigler]

✨ PR Description

Purpose and impact:
This PR introduces new automation features for labeling Pull Requests assisted by Cursor AI, helping track the impact and usage of Cursor's AI capabilities across development workflows.

Main changes:

• Added new documentation for Cursor integration, including methods to label PRs by prompt, known users, and tags
• Created automation files for implementing Cursor PR labeling in different scenarios
• Updated the integrations README to include Cursor under the AI Tools section

Generated by LinearB AI and added by gitStream.
_{AI-generated content may contain inaccuracies. Please verify before using. We’d love your feedback! 🚀}

Screenshots

[orca-security-us]

Orca Security Scan Summary

Status	Check	Issues by priority
Passed	Infrastructure as Code	0   0   0   0	View in Orca
Passed	SAST	0   0   0   0	View in Orca
Passed	Secrets	0   0   0   0	View in Orca
Passed	Vulnerabilities	0   0   0   0	View in Orca

[PavelLinearB]

Looks great!

• Please also add a reference to the cursor integration from the integrations page?

• Future work: Add labels by tag to the general AI micro survey

[BenLloydPearson]

I have a couple of questions:

1. Can you provide screenshots of the new pages you created? It makes it so I don't have to build the docs site locally to see your changes.
2. Does Cursor have the ability to automatically add comments to indicate code that it authored? If so, we should incorporate an example that demonstrates that too.

Also, this needs a button on the /integrations page. We should create a new header for AI and group all of the AI services under that.

[azigler]

@BenLloydPearson Added screenshots.

Does Cursor have the ability to automatically add comments to indicate code that it authored?

Sadly Cursor does not have a comparable feature to GitHub Copilot's experimental code generation labeling.

You could potentially achieve something similar with strong prompting and rules in Cursor, but that's outside the scope of this integration.

We should create a new header for AI and group all of the AI services under that.

I agree. To keep this PR small and focused, I will update the integrations page in a different PR. I am making more AI orchestration examples like this Cursor one, so I will use one PR to list them all on the page.

EDIT: It was easy to make the initial edit now.

[azigler]

@PavelLinearB Is there anything I need to add for this Cursor integration to show in the LinearB automation marketplace? Otherwise, ready for your approval.