npx claudepluginhub nmoinvaz/speedy-gonzales --plugin arribaThis skill uses the workspace's default tool permissions.
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
Searches prompts.chat for AI prompt templates by keyword or category, retrieves by ID with variable handling, and improves prompts via AI. Use for discovering or enhancing prompts.
Compares coding agents like Claude Code and Aider on custom YAML-defined codebase tasks using git worktrees, measuring pass rate, cost, time, and consistency.
Common acli commands for Jira operations used across this project's workflows.
acli must be installed and authenticated: acli jira auth login --webacli jira auth statusThe view command accepts the issue key as a positional argument, but subcommands like comment list, comment create, transition, edit, etc. require the --key flag:
acli jira workitem view PROJ-123 # positional OK
acli jira workitem comment list --key PROJ-123 # --key required
acli jira workitem comment create --key PROJ-123 --body … # --key required
acli jira workitem view PROJ-123
With all fields (description, comments, etc.):
acli jira workitem view PROJ-123 --fields "*all"
JSON output for parsing:
acli jira workitem view PROJ-123 --json
Specific fields only:
acli jira workitem view PROJ-123 --fields "summary,status,priority,description,comment"
acli jira workitem search --jql 'summary ~ "CVE-2024-1234" AND summary ~ "repo-name"' --json
Search by text across all fields:
acli jira workitem search --jql 'text ~ "search terms" AND key != PROJ-123' --json
Search by component:
acli jira workitem search --jql 'component = "my-component" AND key != PROJ-123' --json
Search recently resolved issues:
acli jira workitem search --jql 'text ~ "search terms" AND status in (Resolved, Done, Closed) AND resolved >= -30d' --json
Limit results and select fields:
acli jira workitem search --jql 'project = PROJ' --fields "key,summary,status" --limit 20 --json
acli jira workitem comment create --key PROJ-123 --body "Comment text here"
Multi-line comment from a file:
acli jira workitem comment create --key PROJ-123 --body-file comment.txt
acli jira workitem comment list --key PROJ-123 --json
Or via the view command:
acli jira workitem view PROJ-123 --fields "comment" --json
First check available transitions:
acli jira workitem view PROJ-123 --fields "status" --json
Then transition:
acli jira workitem transition --key PROJ-123 --status "Done"
acli jira workitem transition --key PROJ-123 --status "In Progress"
acli jira workitem transition --key PROJ-123 --status "Resolved"
acli jira workitem create --project PROJ --type Bug --summary "Bug title" --description "Description"
With assignee and labels:
acli jira workitem create --project PROJ --type Task --summary "Title" \
--assignee "user@example.com" --label "bug,triage"
acli jira workitem edit --key PROJ-123 --summary "Updated summary"
acli jira workitem edit --key PROJ-123 --assignee "@me"
The --description and --description-file flags only accept plain text. To set a rich-text description with headings, code blocks, lists, etc., use --from-json with Atlassian Document Format (ADF).
Generate a sample JSON template:
acli jira workitem create --generate-json
acli jira workitem edit --generate-json
Write a JSON file with the ADF description field, then use --from-json:
acli jira workitem create --from-json workitem.json
Write a JSON file with issues and description fields:
{
"issues": ["PROJ-123"],
"description": {
"type": "doc",
"version": 1,
"content": [
{
"type": "heading",
"attrs": {"level": 2},
"content": [{"type": "text", "text": "Section Title"}]
},
{
"type": "paragraph",
"content": [
{"type": "text", "text": "Normal text and "},
{"type": "text", "text": "inline code", "marks": [{"type": "code"}]},
{"type": "text", "text": " in a paragraph."}
]
},
{
"type": "codeBlock",
"attrs": {"language": "json"},
"content": [{"type": "text", "text": "{\"key\": \"value\"}"}]
},
{
"type": "bulletList",
"content": [
{"type": "listItem", "content": [{"type": "paragraph", "content": [{"type": "text", "text": "Bullet item"}]}]}
]
},
{
"type": "orderedList",
"content": [
{"type": "listItem", "content": [{"type": "paragraph", "content": [{"type": "text", "text": "Numbered item"}]}]}
]
}
]
}
}
Then apply:
acli jira workitem edit --from-json workitem.json --yes
| Node | Usage |
|---|---|
heading | attrs.level: 1-6 |
paragraph | Container for text nodes |
codeBlock | attrs.language: json, bash, etc. |
bulletList | Contains listItem nodes |
orderedList | Contains listItem nodes |
text | marks: code, strong, em, link |
--description and --description-file do NOT render wiki markup or markdown — they produce plain text onlycomment create) does not support ADF; comment update does via --body-adfacli jira project list