Skip to content

OLS-0000: Standardize AGENTS.md content#2224

Open
joshuawilson wants to merge 1 commit into
openshift:mainfrom
joshuawilson:ols-0000-standardize-agents-md
Open

OLS-0000: Standardize AGENTS.md content#2224
joshuawilson wants to merge 1 commit into
openshift:mainfrom
joshuawilson:ols-0000-standardize-agents-md

Conversation

@joshuawilson

@joshuawilson joshuawilson commented Jul 14, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Standardize AGENTS.md to include 4 mandatory sections: Specs, Commands, Conventions, Git and PR Workflow
  • Normalize file structure: AGENTS.md is the canonical file, CLAUDE.md is a symlink to it
  • Remove Risk Levels section (hook doesn't work in all cases)

Test plan

  • Verify AGENTS.md has all 4 mandatory sections
  • Verify CLAUDE.md is a symlink to AGENTS.md
  • Verify no Risk Levels section remains

🤖 Generated with Claude Code

Summary by CodeRabbit

  • Documentation
    • Removed the Risk Levels section from the project documentation.

Add missing mandatory sections and remove Risk Levels section
to match the team-wide AGENTS.md template.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@openshift-ci-robot

Copy link
Copy Markdown

@joshuawilson: No Jira issue with key OLS-0000 exists in the tracker at https://redhat.atlassian.net.
Once a valid jira issue is referenced in the title of this pull request, request a refresh with /jira refresh.

Details

In response to this:

Summary

  • Standardize AGENTS.md to include 4 mandatory sections: Specs, Commands, Conventions, Git and PR Workflow
  • Normalize file structure: AGENTS.md is the canonical file, CLAUDE.md is a symlink to it
  • Remove Risk Levels section (hook doesn't work in all cases)

Test plan

  • Verify AGENTS.md has all 4 mandatory sections
  • Verify CLAUDE.md is a symlink to AGENTS.md
  • Verify no Risk Levels section remains

🤖 Generated with Claude Code

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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci Bot requested review from kyoto and xrajesh July 14, 2026 12:38
@coderabbitai

coderabbitai Bot commented Jul 14, 2026

Copy link
Copy Markdown

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: 2c036faf-e7a8-4218-978c-df8cd9674945

📥 Commits

Reviewing files that changed from the base of the PR and between 3c302d6 and ca74e75.

📒 Files selected for processing (1)
  • AGENTS.md
💤 Files with no reviewable changes (1)
  • AGENTS.md

📝 Walkthrough

Walkthrough

The pull request removes the “Risk Levels” section from AGENTS.md, including PreToolUse hook enforcement details and the external risk rubric link.

Changes

Documentation Update

Layer / File(s) Summary
Remove Risk Levels guidance
AGENTS.md
Deletes the Risk Levels documentation, Jira hook enforcement description, and associated rubric link.

Estimated code review effort: 1 (Trivial) | ~2 minutes

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title is concise and broadly matches the AGENTS.md standardization changes, including removal of the Risk Levels section.
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.
✨ 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

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

@openshift-ci-robot

Copy link
Copy Markdown

@joshuawilson: No Jira issue with key OLS-0000 exists in the tracker at https://redhat.atlassian.net.
Once a valid jira issue is referenced in the title of this pull request, request a refresh with /jira refresh.

Details

In response to this:

Summary

  • Standardize AGENTS.md to include 4 mandatory sections: Specs, Commands, Conventions, Git and PR Workflow
  • Normalize file structure: AGENTS.md is the canonical file, CLAUDE.md is a symlink to it
  • Remove Risk Levels section (hook doesn't work in all cases)

Test plan

  • Verify AGENTS.md has all 4 mandatory sections
  • Verify CLAUDE.md is a symlink to AGENTS.md
  • Verify no Risk Levels section remains

🤖 Generated with Claude Code

Summary by CodeRabbit

  • Documentation
  • Removed the Risk Levels section from the project documentation.

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 openshift-eng/jira-lifecycle-plugin repository.

@kyoto

kyoto commented Jul 14, 2026

Copy link
Copy Markdown
Member

/approve
/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Jul 14, 2026
@openshift-ci

openshift-ci Bot commented Jul 14, 2026

Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: kyoto

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

The pull request process is described here

Details Needs approval from an approver in each of these files:

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

@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jul 14, 2026
@joshuawilson

Copy link
Copy Markdown
Contributor Author

/retest

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants