acli-jira
Use when a user wants to create, view, edit, search, comment on, link, assign, or transition Jira issues with the Atlassian CLI (acli). Covers safe ADF (Atlassian Document Format) content. Do not use for implementation, requirements analysis, design documents, or reviews that do not need a Jira operation.
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-14
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- acli-jira
- description
- Use when a user wants to create, view, edit, search, comment on, link, assign, or transition Jira issues with the Atlassian CLI (acli). Covers safe ADF (Atlassian Document Format) content. Do not use for implementation, requirements analysis, design documents, or reviews that do not need a Jira operation.
02 资源文件 5
- 参考文档agents/openai.yaml98 B
- 参考文档references/adf-format.md1.3 KB
- 参考文档references/advanced-operations.md1.5 KB
- 参考文档references/setup.md1.6 KB
- 脚本scripts/jira-client.mjs3.8 KB
03 SKILL.md 正文
ACLI Jira
Use the externally installed acli CLI for Jira operations. Confirm the user's intended project, issue type, fields, and target issue before any mutation. Do not install or authenticate acli as part of this skill.
Setup
Read setup guidance before first use. acli jira auth login --web is the preferred interactive setup. The optional bundled read helper requires a separately configured API token; it never prints or persists that token.
Common operations
# Inspect or search before mutating.
acli jira workitem view PROJ-123 --json
acli jira workitem search --jql "assignee = currentUser()" --fields "key,summary,status"
# Create or update after confirming the supplied values.
acli jira workitem create --project "PROJ" --type "Story" --summary "Concise title" --description "Plain text"
acli jira workitem transition --key PROJ-123 --status "In Progress"
Use --from-json for rich descriptions or comments. ADF must be a complete document object with root type, version, and non-empty content; plain Markdown is not a substitute. Read ADF format before constructing or modifying rich text.
Read helper
The bundled reader provides compact issue, search, and project output without encoding project-specific workflow semantics:
node ./scripts/jira-client.mjs issue PROJ-123
node ./scripts/jira-client.mjs search "assignee = currentUser()" --limit 10 --format json
node ./scripts/jira-client.mjs project PROJ
The helper resolves its shared library through a portable relative import. It is read-only; use acli jira ... for authorized writes.
Mutation guardrails
- Fetch the issue first and preserve fields not explicitly approved for change.
- Use the site's configured issue types, statuses, link types, and fields; do not guess them.
- Create ADF JSON in a local, reviewed file. Check its structure before sending it.
- Never add a secret, access token, cookie, or private user data to an issue or comment.
- Treat parent, sprint, version, attachment, and bulk changes as higher-risk operations; read advanced operations and confirm scope first.
References
04 同仓库更多 Skills
ui-ux-pro-max
UI/UX design intelligence for web and mobile. Local database with 79 searchable styles (88 catalog entries), 192 color palettes, 74 font pairings, 192 product types, 119 UX guidelines, 105 curated icon entries, 17 GSAP motion presets, and 25 chart types across 22 stacks (React, Next.js, Vue, Nuxt, Svelte, Astro, SwiftUI, React Native, Flutter, Tailwind, shadcn/ui, Jetpack Compose, Angular, Laravel, JavaFX, WPF, WinUI, Avalonia, Uno Platform, UWP, Three.js, and HTML/CSS). Use when designing, building, or reviewing UI: pages, components, color schemes, typography, layout, accessibility, animation, or data visualization.
figma-mcp
Implement or compare UI against Figma designs using an available Figma MCP integration. Use for Figma-backed implementation, design-token extraction, or visual-parity gap analysis; Figma MCP access is optional and must already be configured by the user.
improve-codebase-architecture
Find evidence-based, active-change architecture improvements using shared design and domain-modeling guidance. Use when a user wants to reduce architectural friction, deepen a module, or make a current change safer, more testable, and easier to navigate.
domain-modeling
Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing GLOSSARY.md or CONTEXT.md, or recording or editing an ADR.
codebase-design
Provide the shared vocabulary and discipline for designing deep modules with clear interfaces and seams. Use when a user wants to design or improve a module, find deepening opportunities, choose a seam, or make code more testable and AI-navigable.
test-coverage-review
MUST invoke to review whether added or updated tests cover code changes in a diff. Checks new logic, branches, error paths, and regression risk, producing a change-to-test matrix. Use requirements-to-tests-traceability for acceptance-criteria mapping and orchestrated-review for bundled reviews.