Skip to content

Conversation

@rikatz
Copy link

@rikatz rikatz commented Dec 4, 2025

What this PR does / why we need it:

Migrate the add-enhancement command from openshift/enhancements to ai-helpers.

This command helps on creating enhancement proposals for Openshift, reusing the existing template to help engineers focus on the writing of the feature and not on replicating the template.

Checklist:

  • Subject and description added to both, commit and PR.
  • Relevant issues have been referenced.
  • This change includes docs.

Summary by CodeRabbit

  • New Features

    • Added a new OpenShift command: /openshift:add-enhancement to create enhancement proposals.
  • Documentation

    • Added a template-driven guide for OpenShift Enhancement Proposals with structured inputs, step-by-step creation flow, writing guidelines, validation checklist, and sections to mark TODOs.

✏️ Tip: You can customize this high-level summary in your review settings.

@openshift-ci openshift-ci bot requested review from brandisher and mrunalp December 4, 2025 19:12
@openshift-ci
Copy link

openshift-ci bot commented Dec 4, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

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

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

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Dec 4, 2025

Walkthrough

Adds a new OpenShift plugin command for creating Enhancement Proposals: introduces a documentation/template Markdown for the command and registers the new command in plugin manifest files (PLUGINS.md, docs/data.json).

Changes

Cohort / File(s) Summary
OpenShift enhancement template
plugins/openshift/commands/add-enhancement.md
New documentation/template file containing YAML front matter for inputs and a step-by-step guide to generate an OpenShift Enhancement Proposal, including sections, writing guidelines, and validation rules.
Plugin registration / CLI metadata
PLUGINS.md, docs/data.json
Added add-enhancement command entry to the OpenShift plugin with arguments <area> <name> <description> <jira>, synopsis, and description to register the new command in CLI metadata and documentation.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

  • Review plugins/openshift/commands/add-enhancement.md for completeness, clarity, and formatting (YAML front matter, TODO handling, section names).
  • Verify consistency between docs/data.json and PLUGINS.md entries (argument hints, synopsis, description).
  • Confirm no unintended changes to other plugin registrations or schema expectations.

Pre-merge checks and finishing touches

Important

Pre-merge checks failed

Please resolve all errors before merging. Addressing warnings is optional.

❌ Failed checks (1 inconclusive)
Check name Status Explanation Resolution
No Assumed Git Remote Names ❓ Inconclusive Unable to access the repository to perform direct examination of code changes; shell script execution failed to clone repository, preventing verification of hardcoded git remote names. Provide direct access to modified files or full file contents from the pull request to ensure no git operations assume remote names without discovery.
✅ Passed checks (6 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title 'Migrate the add-enhancement command to ai-helpers' directly and clearly describes the primary change: moving the add-enhancement command from one repository to another.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
No Real People Names In Style References ✅ Passed The pull request does not contain any references to real people's names in style references, plugin commands, or skill documentation.
Git Push Safety Rules ✅ Passed The pull request contains only documentation and configuration changes with no code behavior modifications or git push operations.
No Untrusted Mcp Servers ✅ Passed The pull request adds documentation and metadata for an OpenShift enhancement proposal creation command with no MCP server installations or untrusted external dependencies.
✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment

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

@openshift-ci
Copy link

openshift-ci bot commented Dec 4, 2025

Hi @rikatz. Thanks for your PR.

I'm waiting for a github.com member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

@openshift-ci openshift-ci bot added the needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. label Dec 4, 2025
@rikatz
Copy link
Author

rikatz commented Dec 4, 2025

/cc @bentito

@openshift-ci openshift-ci bot requested a review from bentito December 4, 2025 19:13
Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (4)
plugins/openshift/commands/add-enhancement.md (4)

10-12: Add language specification to fenced code block.

The synopsis code block should specify a language identifier for proper rendering.

 ## Synopsis
-```
+```bash
 /openshift:add-enhancement <area> <name> <description> <jira>

---

`55-55`: **Grammar: Use "to be included" instead of "wants included".**

```diff
-   - Explicit Goals or Non-Goals the user wants included
+   - Explicit Goals or Non-Goals the user wants to be included

60-60: Reduce consecutive sentences starting with "Ask".

Three successive bullet points begin with "Ask clarifying questions". Consider varying the phrasing for better readability.

-   - Ask clarifying questions about telemetry, security, upgrade and downgrade process, rollbacks, dependencies, in case it is not possible to assert these fields.
+   - Clarify telemetry, security, upgrade and downgrade process, rollbacks, and dependencies in case these fields cannot be asserted.

92-96: Capitalize "Markdown" as a proper noun (formatting language name).

-   - Invalid markdown syntax (e.g., breaking markdown links, code blocks, or formatting)
+   - Invalid Markdown syntax (e.g., breaking Markdown links, code blocks, or formatting)
 
-   If breaking at 80 characters would split a URL, code, or markdown syntax, find the nearest valid break point such as: after a sentence, before a URL starts, after a URL ends, or at a natural paragraph break. For regular prose, it is acceptable to exceed 80 characters by 10-15 characters to avoid breaking words mid-word. Only allow lines >95 characters when the line contains a single unbreakable element (like a standalone URL with no surrounding text, or a single line of code).
+   If breaking at 80 characters would split a URL, code, or Markdown syntax, find the nearest valid break point such as: after a sentence, before a URL starts, after a URL ends, or at a natural paragraph break. For regular prose, it is acceptable to exceed 80 characters by 10-15 characters to avoid breaking words mid-word. Only allow lines >95 characters when the line contains a single unbreakable element (like a standalone URL with no surrounding text, or a single line of code).
📜 Review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Cache: Disabled due to data retention organization setting

Knowledge base: Disabled due to data retention organization setting

📥 Commits

Reviewing files that changed from the base of the PR and between cc161d2 and 7011304.

📒 Files selected for processing (3)
  • PLUGINS.md (1 hunks)
  • docs/data.json (1 hunks)
  • plugins/openshift/commands/add-enhancement.md (1 hunks)
🧰 Additional context used
🪛 LanguageTool
plugins/openshift/commands/add-enhancement.md

[style] ~55-~55: The double modal “wants included” is nonstandard (only accepted in certain dialects). Consider “to be included”.
Context: ...licit Goals or Non-Goals the user wants included - Any specific technical constraints...

(NEEDS_FIXED)


[style] ~60-~60: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...oUpgrade or TechPreviewNoUpgrade). - Ask clarifying questions about telemetry, s...

(ENGLISH_WORD_REPEAT_BEGINNING_RULE)


[uncategorized] ~94-~94: Did you mean the formatting language “Markdown” (= proper noun)?
Context: ...before or after the URL) - Invalid markdown syntax (e.g., breaking markdown links, ...

(MARKDOWN_NNP)


[uncategorized] ~94-~94: Did you mean the formatting language “Markdown” (= proper noun)?
Context: ...Invalid markdown syntax (e.g., breaking markdown links, code blocks, or formatting) ...

(MARKDOWN_NNP)


[uncategorized] ~96-~96: Did you mean the formatting language “Markdown” (= proper noun)?
Context: ... characters would split a URL, code, or markdown syntax, find the nearest valid break po...

(MARKDOWN_NNP)

🪛 markdownlint-cli2 (0.18.1)
plugins/openshift/commands/add-enhancement.md

10-10: Fenced code blocks should have a language specified

(MD040, fenced-code-language)


41-41: Bare URL used

(MD034, no-bare-urls)


44-44: Bare URL used

(MD034, no-bare-urls)


59-59: Bare URL used

(MD034, no-bare-urls)


78-78: Bare URL used

(MD034, no-bare-urls)


78-78: Bare URL used

(MD034, no-bare-urls)


79-79: Bare URL used

(MD034, no-bare-urls)


79-79: Bare URL used

(MD034, no-bare-urls)


80-80: Bare URL used

(MD034, no-bare-urls)

🔇 Additional comments (2)
PLUGINS.md (1)

229-229: Entry is well-formatted and consistent with other documentation.

The new command is properly registered in alphabetical order and follows the established documentation format.

docs/data.json (1)

607-612: JSON structure is valid and consistent with command metadata standards.

Command entry is correctly formatted with matching argument hints and description from PLUGINS.md.

@bentito
Copy link

bentito commented Dec 8, 2025

/ok-to-test

@openshift-ci openshift-ci bot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Dec 8, 2025
@bentito
Copy link

bentito commented Dec 10, 2025

/assign bentito

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

Labels

ok-to-test Indicates a non-member PR verified by an org member that is safe to test.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants