Add risk level rubric to AGENTS.md

[xrajesh]

Adds a Risk Levels section to AGENTS.md defining risk 1/2/3 classification with repo-specific examples and Jira description format.

Summary by CodeRabbit

• Documentation
  • Added a new "Risk Levels" section describing how risk levels are applied before change actions and linking to an external risk-rubric for classification examples.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: 7016092b-fcd2-4858-89f4-cc03845024b4

📥 Commits

Reviewing files that changed from the base of the PR and between ea56f04 and 8f3ff71.

📒 Files selected for processing (1)

• AGENTS.md

✅ Files skipped from review due to trivial changes (1)

• AGENTS.md

---

📝 Walkthrough

Walkthrough

Adds a short "Risk Levels" section to AGENTS.md stating Risk Levels are enforced via a PreToolUse hook before Jira create/edit calls and linking to an external risk-rubric.md with classification examples.

Changes

Risk Levels documentation

Layer / File(s)	Summary
Risk Levels note and external rubric link AGENTS.md	Adds a "Risk Levels" section that states enforcement via a PreToolUse hook for Jira create/edit operations and links to the external risk-rubric.md containing rubric/classification examples.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Title check	⚠️ Warning	The title claims to add a 'risk level rubric' to AGENTS.md, but the actual change only adds a brief note referencing an external rubric document, not the rubric itself.	Revise the title to more accurately reflect the change, such as 'Add risk levels section to AGENTS.md' or 'Reference risk levels rubric in AGENTS.md'.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@AGENTS.md`:
- Line 183: The fenced code block showing the "Risk Level" snippet is missing a
language tag which triggers MD040; update the opening fence for that block (the
triple backticks before the "## Risk Level" content) to include a language
identifier (e.g., use ```text) so the block is fenced with a language tag and
linting passes.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: 955e3bea-e64e-49d1-9c43-83a3579623c4

📥 Commits

Reviewing files that changed from the base of the PR and between 33a264b and ea56f04.

📒 Files selected for processing (1)

• AGENTS.md

[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 tisnik 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

[openshift-ci]

@xrajesh: all tests passed!

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.