chore: add Claude AI skills for CVE resolution workflow [rhoai-3.3]

[ayush17]

Summary

Backport from main: Add Claude Code CLI and Cursor IDE integration for automated CVE resolution.

Files Added

• .claude/commands/fix-cve.md - Main CVE workflow command
• .claude/skills/cve-resolution/SKILL.md - CVE resolution skill
• docs/cves/cve-developer-guide.md - Full workflow documentation

Jira

https://redhat.atlassian.net/browse/RHAIENG-5845

Made with Cursor

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign jiridanek for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[github-actions]

@ayush17 — This PR is from a fork.
The build-rhoai CI job was skipped because subscription
builds (RHEL, AIPCC) need secrets unavailable to forks.
ODH builds and code quality checks still ran.

Recommended: Push your branch to the main repo for full CI:

git remote add upstream https://github.com/red-hat-data-services/notebooks.git
git push upstream HEAD:ayush17/your-branch-name

Then open a new PR from that branch.

No push access? A maintainer will cherry-pick and test your changes.

See CONTRIBUTING.md for details.

[konflux-internal-p02]

Caution

There are some errors in your PipelineRun template.

PipelineRun	Error
odh-workbench-jupyter-pytorch-llmcompressor-cuda-py312-v3-3-push.yaml	yaml validation error: line 77: did not find expected key

[coderabbitai]

Warning

Review limit reached

@ayush17, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 59 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: c5df02b8-e536-45bf-9633-56f19c2b462f

📥 Commits

Reviewing files that changed from the base of the PR and between 66cce0d and 0846da3.

📒 Files selected for processing (13)

• .claude/commands/_TEMPLATE.md
• .claude/commands/fix-cve.md
• .claude/commands/hello.md
• .claude/skills/.keep
• .claude/skills/cve-resolution/SKILL.md
• .cursor/mcp.json.example
• .env.mcp.local.example
• .gitignore
• .mcp.json.example
• CLAUDE.md
• docs/claude-mcp.md
• docs/cves/cve-developer-guide.md
• docs/cves/logs/cve-resolution-log.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[ayush17]

Closing in favor of creating a separate agent skills marketplace repository. Skills will be available via /plugin marketplace add on any branch.