feat(jira): add --ci flag to jira:solve for non-interactive automation - #290
Conversation
openshift-ci
Bot
added
the
approved
WalkthroughAdds an optional Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes 🚥 Pre-merge checks | ✅ 8✅ Passed checks (8 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. 📜 Recent review detailsConfiguration 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 📒 Files selected for processing (4)
🚧 Files skipped from review as they are similar to previous changes (3)
🔇 Additional comments (2)
✏️ Tip: You can disable this entire section by setting Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Fix all issues with AI agents
In `@plugins/jira/commands/solve.md`:
- Line 136: Update the docs for the /jira:solve command to explicitly show that
the remote ($2) defaults to "origin" and that the --ci flag ($3) can be passed
without specifying the remote; add a concise usage example such as "/jira:solve
OCPBUGS-12345 --ci" (and optionally show the equivalent with explicit remote
"/jira:solve OCPBUGS-12345 origin --ci") next to the $3 description so readers
clearly see the default-remote behavior.
🧹 Nitpick comments (1)
plugins/jira/commands/solve.md (1)
19-24: Consider adding a usage example with the--ciflag.The current usage examples section only shows the basic usage without the
--ciflag. Adding an example that demonstrates CI automation mode would improve clarity and help users understand when and how to use this new feature.📝 Suggested addition
**Usage Examples:** 1. **Solve a specific JIRA issue**: ``` /jira:solve OCPBUGS-12345 origin ``` + +2. **Solve a JIRA issue in CI automation mode (non-interactive)**: + ``` + /jira:solve OCPBUGS-12345 origin --ci + ```
📜 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
📒 Files selected for processing (1)
plugins/jira/commands/solve.md
🔇 Additional comments (4)
plugins/jira/commands/solve.md (4)
10-10: LGTM!The synopsis correctly documents the
--ciflag as an optional third parameter using standard CLI documentation conventions.
47-48: LGTM!The conditional behavior for issue grooming is clearly documented. The non-interactive path appropriately proceeds with available information when
--ciis set, which aligns with CI automation requirements.
62-63: LGTM!The conditional behavior for plan review is clearly documented and consistent with the overall non-interactive automation approach when
--ciis set.
123-130: LGTM!The PR description review section clearly documents both the interactive and non-interactive flows. The detailed prompts for the interactive case provide good guidance for implementation.
✏️ Tip: You can disable this entire section by setting review_details to false in your review settings.
| ## Arguments: | ||
| - $1: The JIRA issue to solve (required) | ||
| - $2: The remote repository to push the branch. Defaults to "origin". | ||
| - $3: Optional `--ci` flag for non-interactive CI automation mode. When set, skips all user prompts and proceeds automatically. |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
fd -type f \( -name "solve*" -o -name "*solve*" \) plugins/jira/Repository: openshift-eng/ai-helpers
Length of output: 238
🏁 Script executed:
fd -e sh -e bash "solve" plugins/jira/Repository: openshift-eng/ai-helpers
Length of output: 50
🏁 Script executed:
ls -la plugins/jira/Repository: openshift-eng/ai-helpers
Length of output: 428
🏁 Script executed:
ls -la plugins/jira/commands/Repository: openshift-eng/ai-helpers
Length of output: 859
🏁 Script executed:
cat -n plugins/jira/commands/solve.mdRepository: openshift-eng/ai-helpers
Length of output: 9132
🏁 Script executed:
ls -la plugins/jira/skills/Repository: openshift-eng/ai-helpers
Length of output: 1079
🏁 Script executed:
git ls-files | grep -i solveRepository: openshift-eng/ai-helpers
Length of output: 98
🏁 Script executed:
ls -la plugins/jira/.claude-plugin/ && cat plugins/jira/.claude-plugin/*Repository: openshift-eng/ai-helpers
Length of output: 394
🏁 Script executed:
head -100 plugins/jira/README.mdRepository: openshift-eng/ai-helpers
Length of output: 4455
🏁 Script executed:
find . -name "*.md" -type f | xargs grep -l "Claude Code" | head -5Repository: openshift-eng/ai-helpers
Length of output: 150
🏁 Script executed:
grep -A 20 -B 5 "argument\|positional\|parameter\|\$[0-9]" ./PLUGINS.md | head -80Repository: openshift-eng/ai-helpers
Length of output: 2936
Clarify how the --ci flag can be used with the default remote.
The documentation indicates that $2 (remote) defaults to "origin" and $3 is the optional --ci flag. However, it's unclear whether users can run /jira:solve OCPBUGS-12345 --ci (omitting the remote) or if they must explicitly specify the remote (e.g., /jira:solve OCPBUGS-12345 origin --ci).
Add a usage example that demonstrates using the --ci flag with the default remote to clarify this behavior for users.
🤖 Prompt for AI Agents
In `@plugins/jira/commands/solve.md` at line 136, Update the docs for the
/jira:solve command to explicitly show that the remote ($2) defaults to "origin"
and that the --ci flag ($3) can be passed without specifying the remote; add a
concise usage example such as "/jira:solve OCPBUGS-12345 --ci" (and optionally
show the equivalent with explicit remote "/jira:solve OCPBUGS-12345 origin
--ci") next to the $3 description so readers clearly see the default-remote
behavior.
|
/lgtm |
openshift-ci
Bot
added
lgtm
openshift-merge-robot
added
the
needs-rebase
Add optional --ci flag ($3) that skips all user interaction points: - Skip asking for issue grooming when required sections are missing - Skip plan review and proceed immediately with implementation - Skip PR description review after creation This enables running jira:solve in CI automation without user prompts. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
ae4eeb7 to
234ab6a
Compare
openshift-merge-robot
removed
the
needs-rebase
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: bryan-cox, celebdor The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
3 participants
Summary
--ciflag ($3) to jira:solve command that skips all user interaction pointsChanges
When
--ciflag is passed:Usage
Test plan
🤖 Generated with Claude Code
Summary by CodeRabbit
New Features
Documentation
Chores
✏️ Tip: You can customize this high-level summary in your review settings.