Skip to content

fix(jira-solve): remove inline verification block from solve command - #620

Merged
openshift-merge-bot[bot] merged 4 commits into
openshift-eng:mainfrom
enxebre:drop-inline-verification-from-solve
Jul 14, 2026
Merged

openshift-merge-bot[bot] merged 4 commits into
openshift-eng:mainfrom
enxebre:drop-inline-verification-from-solve

Conversation

@enxebre

@enxebre enxebre commented Jul 14, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Remove the 22-line inline verification block from the jira:solve command that instructed the agent to run make lint-fix, make verify, and make test explicitly during the solve phase

Why

These checks are already enforced by pre-commit and pre-push git hooks. Having them duplicated inline causes the agent to run the full test suite twice per session — once explicitly in the solve phase, and once via the pre-push hook when pushing. On CI pods with limited CPU (500m currently, being bumped in openshift/release#81875), make test -race across 374 packages takes 30+ minutes per run, so the duplication doubles session time and increases the chance of hitting GitHub token expiry (CNTRLPLANE-3835).

Related

🤖 Generated with Claude Code

Summary by CodeRabbit

  • Documentation
    • Updated jira:solve command guidance by removing the repository verification procedure and related build/lint/test and commit-blocking instructions.
  • Chores
    • Bumped the Jira plugin version from 0.8.3 to 0.8.4.
    • Bumped the OpenShift Developer bundle version from 1.1.9 to 1.1.10 and updated its Jira dependency requirement to ^0.8.4.
    • Refreshed the embedded marketplace versions to match the above changes.

Verification (make lint-fix, make verify, make test) is already
enforced by pre-commit and pre-push hooks. Having it duplicated
inline in the solve command causes the agent to run the full test
suite twice — once explicitly and once via the push hook — doubling
session time and increasing the chance of hitting token expiry.

Tracks: CNTRLPLANE-3761

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@openshift-ci
openshift-ci Bot requested review from bryan-cox and cblecker July 14, 2026 14:55
@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
@coderabbitai

coderabbitai Bot commented Jul 14, 2026

Copy link
Copy Markdown
Contributor

Walkthrough

The jira:solve documentation removes its repository verification procedure. Jira is updated to version 0.8.4, while OpenShift Developer is updated to 1.1.10 with its Jira dependency raised to ^0.8.4.

Changes

Jira workflow and release updates

Layer / File(s) Summary
Simplify Jira solve workflow
plugins/jira/commands/solve.md
The implementation workflow now transitions directly to commit creation without the removed verification instructions.
Synchronize plugin release metadata
plugins/jira/.claude-plugin/plugin.json, plugins/openshift-developer/.claude-plugin/plugin.json, docs/index.html
Jira and OpenShift Developer versions are updated in plugin manifests and marketplace data; the OpenShift Developer Jira dependency is updated to ^0.8.4.

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

Possibly related PRs

Suggested reviewers: cblecker, brandisher, bentito, bryan-cox

🚥 Pre-merge checks | ✅ 10
✅ Passed checks (10 passed)
Check name Status Explanation
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.
No Real People Names In Style References ✅ Passed No real-person names appear as style references or examples in the edited plugin docs/manifests.
No Assumed Git Remote Names ✅ Passed The commit only bumps versions in docs/index.html and the Jira dependency manifest; no changed lines hardcode a remote like origin/upstream.
Git Push Safety Rules ✅ Passed The PR only removes verification docs and bumps versions; the diff adds no git push, force-push, or main/master push instructions.
No Untrusted Mcp Servers ✅ Passed The diff only bumps plugin/docs versions and removes Jira verification text; no new MCP server packages, repos, or npx installs appear.
Ai-Helpers Overlap Detection ✅ Passed No overlapping ai-helper functionality found: nearby open PRs touch different commands/paths, and solve.md is closest to generate-test-plan at ~36% token overlap.
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly matches the main change: removing the inline verification block from the jira:solve command.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

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

enxebre and others added 2 commits July 14, 2026 17:01
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

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 `@plugins/jira/.claude-plugin/plugin.json`:
- Line 4: Synchronize the version metadata for the release declared in the
plugin manifest at 0.8.4. Run the repository’s established version-sync
workflow, ensuring .claude-plugin/marketplace.json and docs/index.html are
regenerated to advertise 0.8.4 consistently.
🪄 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: a684b3ca-d59e-4462-b2e0-4b259774d244

📥 Commits

Reviewing files that changed from the base of the PR and between 88d0e88 and 2e14569.

📒 Files selected for processing (1)
  • plugins/jira/.claude-plugin/plugin.json

"name": "jira",
"description": "A plugin to automate tasks with Jira",
"version": "0.8.3",
"version": "0.8.4",

@coderabbitai coderabbitai Bot Jul 14, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

🗄️ Data Integrity & Integration | 🟠 Major | ⚡ Quick win

Synchronize downstream Jira version metadata.

The manifest now declares 0.8.4, but .claude-plugin/marketplace.json and docs/index.html still advertise 0.8.3. Run the repository’s version-sync workflow and commit the generated updates so marketplace consumers and documentation resolve the same release version.

🤖 Prompt for 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.

In `@plugins/jira/.claude-plugin/plugin.json` at line 4, Synchronize the version
metadata for the release declared in the plugin manifest at 0.8.4. Run the
repository’s established version-sync workflow, ensuring
.claude-plugin/marketplace.json and docs/index.html are regenerated to advertise
0.8.4 consistently.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

This is a false positive — docs/index.html is already updated to 0.8.4 in this PR (see the diff for that file). There is no marketplace.json in the jira plugin directory either. The versions are synchronized.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
fd -i marketplace.json
echo "---"
rg -n "0\.8\.[0-9]" docs/index.html
echo "---"
rg -n "\"version\"" plugins/jira/.claude-plugin/plugin.json

Length of output: 354


@bryan-cox You're right — I confirmed there's no marketplace.json file anywhere in the repository, and docs/index.html already shows "version": "0.8.4" at Line 1416, matching the manifest. The versions are indeed synchronized. Thanks for catching that false positive.

(=^・ω・^=) apologies for the noise!

@bryan-cox bryan-cox left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

/lgtm

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

Copy link
Copy Markdown
Contributor

/hold

@openshift-ci openshift-ci Bot added do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. and removed lgtm Indicates that a PR is ready to be merged. labels Jul 14, 2026
Pick up jira plugin 0.8.4 which removes the inline verification
block from the solve command.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@enxebre
enxebre force-pushed the drop-inline-verification-from-solve branch from bc299f6 to d621dc4 Compare July 14, 2026 15:06
@bryan-cox

Copy link
Copy Markdown
Contributor

/hold cancel

@openshift-ci openshift-ci Bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jul 14, 2026

@bryan-cox bryan-cox left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

/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
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bryan-cox, enxebre

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-merge-bot
openshift-merge-bot Bot merged commit cedab04 into openshift-eng:main Jul 14, 2026
6 checks passed
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.

2 participants