- Home
- Skills
- Grandcamel
- Jira Assistant Skills
- Jira Collaborate
jira-collaborate_skill
- Shell
4
GitHub Stars
1
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill grandcamel/jira-assistant-skills --skill jira-collaborate- SKILL.md9.4 KB
Overview
This skill provides collaboration tools for JIRA issues: manage comments, attachments, watchers, notifications, and view activity history. It is designed for team communication and coordination around issue work without touching workflow transitions. Always run commands through the jira-as CLI as documented.
How this skill works
The skill exposes CLI commands to add, update, list, and delete comments (including role/group visibility and rich-text formats). It supports uploading, listing, and downloading attachments, managing watchers, sending targeted notifications, and querying the issue changelog. Commands accept JSON or text outputs and include pagination and preview/dry-run options for safer operations.
When to use it
- Posting progress updates, internal notes, or technical explanations on an issue
- Uploading or retrieving evidence files, logs, or screenshots tied to an issue
- Adding or removing watchers to ensure the right people are notified
- Sending targeted notifications to users, groups, assignee, or reporter
- Reviewing activity history or changelog to audit recent changes
- Updating custom fields while collaborating on issue details
Best practices
- Use --dry-run or preview options before destructive operations like delete
- Prefer account IDs (not emails) for watcher and notify commands to avoid ambiguity
- Use visibility-role or visibility-group for internal-only comments
- List comments or attachments first to confirm IDs before update/delete
- Run all operations via the jira-as CLI; do not execute underlying scripts directly
Example use cases
- Add a rich-text progress comment and notify watchers that work has started
- Upload a screenshot as evidence and link it in a follow-up comment
- List recent activity to prepare handoff notes for the next assignee
- Remove an external watcher after issue confidentiality changes
- Preview a notification to confirm recipients before sending to a large group
FAQ
Preview the item with list commands and use --dry-run when available. Deletions are destructive; attachments must be re-uploaded if lost.
Can I send notifications without actually sending them?
Yes. Use the --dry-run option on notify commands to preview recipients and message content.