From 260661bfe138f2fe3fef43ddeaf93e168af7dab3 Mon Sep 17 00:00:00 2001 From: Bryan Cox Date: Wed, 14 Jan 2026 09:51:01 -0500 Subject: [PATCH 1/3] feat(jira): add --ci flag to jira:solve for non-interactive automation 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 --- plugins/jira/commands/solve.md | 23 ++++++++++++++--------- 1 file changed, 14 insertions(+), 9 deletions(-) diff --git a/plugins/jira/commands/solve.md b/plugins/jira/commands/solve.md index e07d0a973..04e82f8ed 100644 --- a/plugins/jira/commands/solve.md +++ b/plugins/jira/commands/solve.md @@ -7,7 +7,7 @@ jira:solve ## Synopsis ``` -/jira:solve [remote] +/jira:solve [remote] [--ci] ``` ## Description @@ -44,7 +44,8 @@ This command takes a JIRA URL, fetches the issue description and requirements, a - Optional - Steps to reproduce (for bugs) - Expected vs actual behavior - - Ask the user for further issue grooming if the requried sections are missing + - If `--ci` flag ($3) is NOT set: Ask the user for further issue grooming if the required sections are missing + - If `--ci` flag ($3) IS set: Proceed with available information, making reasonable assumptions where needed 2. **Codebase Analysis**: Search and analyze relevant code: - Find related files and functions @@ -58,7 +59,8 @@ This command takes a JIRA URL, fetches the issue description and requirements, a 3. **Solution Implementation**: - Think hard and create a detailed, step-by-step plan to implement this feature. Save it to spec-$1.md within the .work/jira/solve folder, for example .work/jira/solve/spec-OCPBUGS-12345.md - - Always ask the user to review the plan and give them the choice to modify it before start the implementation + - If `--ci` flag ($3) is NOT set: Ask the user to review the plan and give them the choice to modify it before starting the implementation + - If `--ci` flag ($3) IS set: Proceed immediately with implementation without waiting for approval - Implement the plan: - Make necessary code changes using Edit/MultiEdit tools - Follow existing code patterns and conventions @@ -118,16 +120,19 @@ This command takes a JIRA URL, fetches the issue description and requirements, a 6. **PR Description Review**: - After creating the PR, display the PR URL and description to the user - - Ask the user: "Please review the PR description. Would you like me to update it? (yes/no)" - - If the user says yes or requests changes: - - Ask what changes they'd like to make - - Update the PR description using `gh pr edit {PR_NUMBER} --body "{new_description}"` - - Repeat this review step until the user is satisfied - - If the user says no or is satisfied, acknowledge and provide next steps + - If `--ci` flag ($3) is NOT set: + - Ask the user: "Please review the PR description. Would you like me to update it? (yes/no)" + - If the user says yes or requests changes: + - Ask what changes they'd like to make + - Update the PR description using `gh pr edit {PR_NUMBER} --body "{new_description}"` + - Repeat this review step until the user is satisfied + - If the user says no or is satisfied, acknowledge and provide next steps + - If `--ci` flag ($3) IS set: Skip the review step and proceed to completion ## 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. The command will provide progress updates and create a comprehensive solution addressing all requirements from the JIRA issue. From 464165f996aaec3627f3b77d1b28ba59bc02c825 Mon Sep 17 00:00:00 2001 From: Bryan Cox Date: Wed, 14 Jan 2026 10:04:06 -0500 Subject: [PATCH 2/3] chore: bump jira plugin version and run make update Co-Authored-By: Claude Opus 4.5 --- docs/data.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/data.json b/docs/data.json index 3b6e789bd..3e2c0fc0b 100644 --- a/docs/data.json +++ b/docs/data.json @@ -136,7 +136,7 @@ "argument_hint": "", "description": "Analyze a JIRA issue and create a pull request to solve it.", "name": "solve", - "synopsis": "/jira:solve [remote]" + "synopsis": "/jira:solve [remote] [--ci]" }, { "argument_hint": "issue-id [--start-date YYYY-MM-DD] [--end-date YYYY-MM-DD]", From 234ab6ad829d1f10861a6e7276dd0626669949ef Mon Sep 17 00:00:00 2001 From: Bryan Cox Date: Wed, 14 Jan 2026 10:26:18 -0500 Subject: [PATCH 3/3] chore: bump jira plugin version to 0.0.4 --- .claude-plugin/marketplace.json | 2 +- docs/data.json | 2 +- plugins/jira/.claude-plugin/plugin.json | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/.claude-plugin/marketplace.json b/.claude-plugin/marketplace.json index 3e7ee16a3..3473357c5 100644 --- a/.claude-plugin/marketplace.json +++ b/.claude-plugin/marketplace.json @@ -20,7 +20,7 @@ "name": "jira", "source": "./plugins/jira", "description": "A plugin to automate tasks with Jira", - "version": "0.0.3" + "version": "0.0.4" }, { "name": "ci", diff --git a/docs/data.json b/docs/data.json index 3e2c0fc0b..8ade4410e 100644 --- a/docs/data.json +++ b/docs/data.json @@ -232,7 +232,7 @@ "name": "OCPBUGS Jira Conventions" } ], - "version": "0.0.3" + "version": "0.0.4" }, { "commands": [ diff --git a/plugins/jira/.claude-plugin/plugin.json b/plugins/jira/.claude-plugin/plugin.json index cab82b502..449c36630 100644 --- a/plugins/jira/.claude-plugin/plugin.json +++ b/plugins/jira/.claude-plugin/plugin.json @@ -1,7 +1,7 @@ { "name": "jira", "description": "A plugin to automate tasks with Jira", - "version": "0.0.3", + "version": "0.0.4", "author": { "name": "github.com/openshift-eng" }