[nwparker]

	Files	Added	Deleted	Net
Test	5	$\color{#1a7f37}{\Huge{\mathbf{+}}}$​638	$\color{#cf222e}{\Huge{\mathbf{−}}}$​10	$\color{#1a7f37}{\Huge{\mathbf{+}}}$​628
Prod	36	$\color{#1a7f37}{\Huge{\mathbf{+}}}$​1448	$\color{#cf222e}{\Huge{\mathbf{−}}}$​112	$\color{#1a7f37}{\Huge{\mathbf{+}}}$​1336

ELI5

Agents can now work on Jira tickets from the terminal: read them, create tickets, leave comments, change status, assign people, set priorities, and edit labels. They use the Jira account already connected to the Orca host they are working on.

What Changed

Before, Jira worked in the Tasks panel but had no agent command surface. This adds the complete orca jira command family, human-readable and JSON output, and the orca-jira / jira-tickets discovery guides. Project keys resolve to real project IDs before creation; project issue types and required create fields are discoverable. Multiline descriptions/comments support files and stdin using the existing body-reading implementation.

Each operation pins one saved Jira site. Browse URLs match the complete site origin and context path; ambiguous keys and conflicting sites fail before writing. Read failures remain errors, while a successful empty comment list remains a success. Status changes resolve against the issue's available transitions, and label add/remove use Jira's atomic operations so unrelated labels survive concurrent edits. Failed or uncertain writes never print success and are not retried automatically.

Why

A read-only CLI cannot complete a Jira task. This follows the established command registry and existing host-owned Jira methods, with optional verified-read and label-operation fields negotiated through jira.agent-access.v1. Older hosts receive update guidance before an agent reads or writes; older clients retain existing behavior. Separate credentials, transports, legacy link storage, and read-only aliases would add competing paths without completing the task.

Linked Issue

Fixes #11982.

Visual Proof

N/A — command-line commands and backend read/mutation handling; no renderer layout or visual interaction changed. A compiled-CLI demonstration over a temporary fixture socket verified reads, successful empty comments, multiline create/comment bodies, transitions, atomic label edits, and refusal of an older host before any Jira write. All demonstration data was synthetic; no real Jira account was contacted.

$ orca jira issue eng-1
ENG-1 Fixture login bug
URL: https://fixture.atlassian.net/browse/ENG-1
Status: Open (To Do)

$ orca jira label add ENG-1 --label bug --json
{"ok":true,"result":{"ok":true,"key":"ENG-1","siteId":"fixture-site"}}

# An older host refuses the command before sending a Jira mutation:
{"ok":false,"error":{"code":"incompatible_runtime"}}

Testing

• I manually tested these changes locally
• Automated tests added/updated, or explained why not below

Reproduced the missing command surface against the starting main commit. On macOS, focused CLI/RPC/backend tests and adjacent command-registry, vocabulary, startup-name, Linear, Jira-query, skill, and guide suites passed. The final guide/read/CLI check ran 116 tests; a follow-up manifest extraction passed direct lint, the CLI typecheck and 44 routing/Jira tests; the preceding focused check ran 111 tests. Coverage includes wrong-site URLs, ambiguous keys, old-host write refusal, genuine empty reads, real read errors, mutation rejections, transition ambiguity, uncertain-write handling, and atomic label edits for Cloud and Server/DC.

pnpm tc:cli, the CLI compiler/bin verification, changed-code quality gate, bundled-guide/skill-manifest/RPC-catalog verification, and git diff --check passed. The reviewed merged head d60f71e072f also passed node and CLI product typechecks after incorporating current main. The prior clock issue is resolved on main; #28593 was closed as redundant. CI must cover the full build and native platforms. Live Jira credentials, Linux, Windows, and a real SSH host were not exercised; remote command routing and Server/DC request shapes are covered by fixtures.

Review

Adapted the full command surface, formatting and guide from #11986 by Dan Cieslak (@dcieslak19973), with exact-site selection and honest saved-connection reporting informed by #26055 by kokbee (@kokbee). Both authors are credited in commit trailers. These source PRs are alternatives; this PR implements a single complete surface instead of landing both unchanged.

Agent skill upstream boundary

• Not applicable, or this change copies or mechanically translates no upstream skill-installer source, tests, fixtures, registry entries, path tables, comments, or documentation.

Notes

Merge risk: Medium. This is a complete new command family, plus small optional backend changes required to avoid misleading reads and unsafe label replacement. Old-client defaults are preserved and new semantics require a capability check. Creation/comments are intentionally not retried after uncertainty. The Cloud-filter and transition-field PRs touch nearby query/schema methods and require integration review; preserve their newer query ownership and optional transition fields when resolving overlap.

Credentials and Jira requests stay on the selected execution host. Commands use no shell commands or platform-specific paths, work independently of git/folder workspace state, and add no mobile/UI requirement or new stream opcode. No original PR was merged, closed, or modified.

Checklist

• This PR is small and focused
• I explained what changed and why (ELI5, the user-facing before/after, the mechanism, and why over the alternatives)
• Before/after screenshots or videos attached for UI changes, or N/A with reason
• Self-reviewed for correctness, security, and performance
• Cross-platform, SSH/remote, and path/shortcut impact considered (or N/A)
• pnpm lint, pnpm typecheck, pnpm test, and pnpm build pass (or CI will cover; local preferred) — focused validation above passed; full CI/native build remain.

[coderabbitai]

Warning

Review limit reached

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

Next included review available in 2 minutes.

Check out review usage here.

View limit details

Limit details: You’ve used all 10 included reviews currently available.

Learn how review limits work.

Review configuration:

⚙️ Run configuration

• Configuration used: Repository UI
• Review profile: CHILL
• Plan: Advanced
• Run ID: a372b39e-cbbf-4f98-bd94-63603c44c142

📥 Commits

Reviewing files that changed from the base of the PR and between fe4fcf1 and d60f71e.

📒 Files selected for processing: 4

• skill-guides/orca-jira.md
• src/cli/bundled-skill-guides.ts
• src/cli/handlers/jira-write.ts
• src/cli/index-jira.test.ts

📝 Walkthrough

The pull request adds a Jira CLI surface for issue reads, searches, metadata discovery, creation, comments, status changes, and field and label updates. It adds strict site and read-error handling across Jira runtime and RPC calls, plus atomic label add/remove operations. It also adds Jira skill guides, registers them as bundled guides, and adds shared command-body input handling used by Jira and Linear.

Priority: ➖ Normal

Severity of issue fixed: Medium

Merge Risk: 🟡 Moderate · up to fe4fc

Clarify authorization before agents create follow-up issues, and correct the completion workflow before merging. The transition-flag message is a smaller usability fix.

Pre-merge checks: 4 · 1

Failed checks: 1 warning

Check name	Status	Explanation	Resolution
Docstring Coverage		Docstring coverage is 9.76% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 41 functions across 34 files. (7 skipped: …	Write docstrings for the functions missing them to satisfy the coverage threshold.

Passed checks: 4 passed

Check name	Status	Explanation
Title check		The title clearly and concisely describes the primary change: adding safe Jira ticket read and update capabilities for agents.
Description check		The description covers the required sections, explains the user-facing changes and rationale, links issue #11982, documents testing and limitations, and addresses security and compatibility considerat…
Linked Issues check		Active direct issue #11982 requires a Jira CLI over existing RPC methods, commands for issue reads/search, creation, comments, transitions, assignees, priorities, labels, and project metadata, human-r…
Out of Scope Changes check		The changes stay within #11982. The shared body-input helper and Linear delegation support the required multiline Jira and existing Linear body behavior. Strict Jira read handling, exact site selectio…

Full details: Docstring Coverage

Explanation

Docstring coverage is 9.76% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 41 functions across 34 files. (7 skipped: 7 unsupported.)

✨ Finishing Touches: 💡 1

📝 Generate docstrings: 💡

• Commit to this branch
• Create a new PR

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

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

• X
• Mastodon
• Reddit
• LinkedIn

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

[coderabbitai]

Actionable comments posted: 3

---

ℹ️ Review info

⚙️ Run configuration

• Configuration used: Repository UI
• Review profile: CHILL
• Plan: Advanced
• Run ID: 6dda33fc-3785-42da-a7d1-a24b3c758f01

📥 Commits

Reviewing files that changed from the base of the PR and between 9c0420f and fe4fcf1.

📒 Files selected for processing: 41

• config/scripts/generate-bundled-skill-guides.mjs
• resources/skills/current-manifest.json
• skill-guides/jira-tickets.md
• skill-guides/orca-jira.md
• skill-stubs/jira-tickets.md
• skill-stubs/orca-jira.md
• skills/jira-tickets/SKILL.md
• skills/orca-jira/SKILL.md
• src/cli/args.ts
• src/cli/bundled-skill-guides.ts
• src/cli/command-body-input.ts
• src/cli/handler-group-manifest.ts
• src/cli/handlers/jira-write.ts
• src/cli/handlers/jira.ts
• src/cli/index-jira.test.ts
• src/cli/jira-command-surface.test.ts
• src/cli/jira-format.ts
• src/cli/jira-handler-group.ts
• src/cli/jira-target.ts
• src/cli/linear-request-builders.ts
• src/cli/reference-handler-group.ts
• src/cli/specs/index.ts
• src/cli/specs/jira.ts
• src/main/jira/jira-agent-read.test.ts
• src/main/jira/jira-issue-comments.ts
• src/main/jira/jira-issue-create-metadata.ts
• src/main/jira/jira-issue-mutations.test.ts
• src/main/jira/jira-issue-mutations.ts
• src/main/jira/jira-issue-read.ts
• src/main/jira/jira-issue-search.ts
• src/main/jira/jira-project-queries.ts
• src/main/jira/jira-read-failure.ts
• src/main/jira/jira-transition-queries.ts
• src/main/runtime/rpc/methods/jira.test.ts
• src/main/runtime/rpc/methods/jira.ts
• src/main/runtime/runtime-jira-commands.ts
• src/main/startup/cli-command-names.ts
• src/shared/jira-agent-capability.ts
• src/shared/jira-types.ts
• src/shared/protocol-version.ts
• src/shared/rpc-contract/jira-params.ts

Included review availability: This review used your included allowance. Your plan provides up to 10 included reviews per hour; 2 remain after this review.

[kokbee]

Thanks for your work on this 😄