
aide
AI agent integration with Jira, Azure DevOps, and GitHub
- version
- 0.0.22
- GitHub stars
- 5
Install
/plugin install aide@aide-marketplaceRun it inside Claude Code after adding the marketplace with /plugin marketplace add rlcurrall/aide.
Contents
Discovered from sourceSkills 21
List Jira Boards
List boards in Jira, optionally filtered by project key.
When to Use
- User asks "what boards are there?" or "find the board for project X"
- User needs a board ID to query sprints
- User wants to see "what's on the board" (first step: find the board)
How to Execute
Run:
aide jira boards [project] [--format text|json|markdown]
Arguments
| Argument | Description |
|---|---|
project | Project key to filter boards (e.g., PROJ) |
Flags
| Flag | Description |
|---|---|
--format | Output format: text, json, markdown |
Examples
# List all boards
aide jira boards
# List boards for a specific project
aide jira boards PROJ
Output Includes
- Board ID (needed for sprint queries)
- Board name
- Board type (scrum, kanban, simple)
- Associated project
Next Steps
After finding a board:
- Use sprint skill to get the active sprint for the board
- Use ticket-search skill with
--sprint-boardflag to search within the active sprint
Post PR Comment
Post a comment on a pull request thread.
When to Use
- User wants to add a general comment to a PR
- User wants to comment on a specific file or line
- User wants to request re-review after changes
- User wants to document a decision or explanation
How to Execute
Run:
aide pr comment "comment text" [--pr <id>] [options]
Flags
| Flag | Description |
|---|---|
--pr | PR ID or URL (auto-detected from branch if omitted) |
--file | File path to attach comment to |
--line | Line number in file (requires --file) |
--end-line | End line for multi-line comment range |
Output Includes
- Thread ID
- Comment content
- File and line location (if specified)
- Timestamp
Common Patterns
# General PR comment (auto-detect PR from branch)
aide pr comment "Ready for re-review after addressing all feedback"
# Comment on specific PR
aide pr comment "LGTM!" --pr 24094
# Comment on specific file
aide pr comment "Consider refactoring this section" --pr 24094 --file src/auth.ts
# Comment on specific line
aide pr comment "Added null check as suggested" --pr 24094 --file src/utils/helpers.ts --line 127
Use Cases
| Purpose | Example |
|---|---|
| Request review | "Ready for re-review after addressing all feedback" |
| Acknowledge feedback | "Good point, I've updated the implementation" |
| Ask questions | "Should this use async/await or promises?" |
| Document decisions | "Using OAuth 2.0 with PKCE for enhanced security" |
| Mark completion | "All comments addressed, tests passing" |
Best Practices
- Be specific when commenting on code locations
- Use line comments for inline feedback
- Use general comments for overall PR updates
- Keep comments constructive and actionable
Next Steps
After posting a comment:
- Use pr-comments skill to verify your comment was posted
- Use pr-reply skill to respond to specific threads
Load PR Comments
Fetch PR comments to review feedback from reviewers.
When to Use
- User asks "what feedback is there?" or "show me the comments"
- User wants to check for unresolved review comments
- User needs to understand what changes reviewers are requesting
- User wants to see discussion history on a PR
How to Execute
Run:
aide pr comments [--pr <id|url>] [options]
Flags
| Flag | Description |
|---|---|
--pr | PR ID or URL (auto-detected from branch if omitted) |
--latest | Limit to N most recent comments |
--thread-status | Filter by thread status: active, fixed, closed |
--author | Filter by reviewer email or name |
--include-system | Include system-generated comments (default: false) |
--format | Output format: text, json, markdown |
Output Includes
Comments organized by:
- File path and line number
- Thread status (active, fixed, etc.)
- Author and timestamp
- Comment content
Best Practices
- Use
--thread-status activeto focus on unresolved feedback - Use
--latest Nto see most recent discussion - Filter by
--authorto see specific reviewer's feedback - Use
--format jsonfor structured processing
PR Review Workflow
# View all active (unresolved) threads
aide pr comments --thread-status active
# Get latest 10 comments
aide pr comments --latest 10
# See specific reviewer's feedback
aide pr comments --author "senior.dev@company.com"
# Get structured data for analysis
aide pr comments --format json
Addressing Feedback
After loading comments:
- Prioritize: Address blocking/critical feedback first
- Understand context: Read the full thread, not just latest comment
- Implement fixes: Make changes based on feedback
- Respond: Use pr-reply skill to acknowledge and explain changes
Next Steps
After reviewing comments:
- Use pr-reply skill to respond to specific threads
- Use pr-comment skill to post general updates
- Use pr-diff skill to see the code being discussed
Create Pull Request
Create a new pull request from the current branch.
When to Use
- User says "create a PR" or "open a pull request"
- User wants to submit code for review
- User has finished changes and needs to merge
- User wants to create a draft PR for early feedback
How to Execute
Run:
aide pr create --title "Title" [options]
Flags
Supports both GitHub CLI and Azure CLI style flags:
| Flag (gh-style) | Short | Aliases (az-style) | Description |
|---|---|---|---|
--title | -t | - | PR title (required) |
--body | -b | --description | PR description/body |
--head | -H | --source, -s, --source-branch | Source/head branch (defaults to current branch) |
--base | -B | --target, --target-branch | Target/base branch (defaults to main) |
--draft | -d | - | Create as draft PR |
--tag | - | - | Add tag(s) to the PR (repeatable) |
Output Includes
- PR ID and URL
- Title and description
- Source and target branches
- Status (draft or active)
Best Practices
- Use descriptive titles that summarize the change
- Include ticket references in title (e.g., "PROJ-123: Add feature")
- Start as draft if work is incomplete
- Always include a meaningful description
Common Patterns
# Basic PR creation
aide pr create --title "Add user authentication"
# With description
aide pr create --title "PROJ-123: Add OAuth" --body "Implements OAuth 2.0 with PKCE flow"
# Draft PR for early feedback
aide pr create --title "WIP: Refactor auth module" --draft
# Targeting specific branch
aide pr create --title "Hotfix: Login bug" --base release/v2.0
# With tags
aide pr create --title "PROJ-123: Fix performance" --tag bug --tag performance
PR Management Workflow
- Prepare branch: Ensure all changes are committed and pushed
- Create PR: Use appropriate flags for title, description, target
- Draft mode: Use
--draftfor work-in-progress - Monitor: Use pr-comments skill to track feedback
- Publish: Use pr-update skill with
--publishwhen ready
Next Steps
After creating a PR:
- Share the PR URL with reviewers
- Use pr-comments skill to monitor feedback
- Use pr-update skill to publish draft when ready
View Pull Request Diff
View changes in a pull request including file diffs and change statistics.
When to Use
- User asks "what changed?" or "show me the changes"
- User wants to review code before approving
- User needs to understand the scope of modifications
- User wants to see a specific file's changes
How to Execute
Run:
aide pr diff [--pr <id|url>] [options]
Options
| Flag | Description |
|---|---|
--pr | PR ID or URL (auto-detected from branch if omitted) |
--stat | Show summary statistics with line counts |
--files | Show only changed file paths |
--file | Show diff for a specific file path |
--no-fetch | Skip auto-fetching missing branches (fetch by default) |
Output Includes
- Source and target branches
- Changed files with +/- line counts (with
--stat) - Full unified diff output (default)
- File list only (with
--files)
Best Practices
- Start with
--statto get an overview of changes - Use
--filesto see which files were modified - Focus on specific files with
--file <path>for detailed review - Auto-fetch is enabled by default - use
--no-fetchif branches are already local
Progressive Review Pattern
# 1. Get overview of changes
aide pr diff --stat
# 2. See which files changed
aide pr diff --files
# 3. Review specific file
aide pr diff --file src/auth/login.ts
Next Steps
After viewing PR diff:
- Use pr-comments skill to see related feedback
- Use pr-view skill for PR metadata
List Pull Requests
List pull requests from the repository with filtering options.
When to Use
- User asks "what PRs are open?" or "show me the PRs"
- User wants to find PRs to review
- User wants to check their own open PRs
- User wants to browse completed/merged PRs
How to Execute
Run:
aide pr list [options]
Flags
| Flag | Description |
|---|---|
--status | Filter by status: active, completed, abandoned, all (default: active) |
--limit | Maximum number of PRs to return (default: 20) |
--created-by | Filter by creator email or display name |
--author | Alias for --created-by |
--project | Project name (auto-discovered from git remote) |
--repo | Repository name (auto-discovered from git remote) |
--format | Output format: text, json, markdown |
Output Includes
- PR number and title
- Status (active, completed, abandoned)
- Creation date
- Author name
- Description preview
Common Patterns
# List active PRs (default)
aide pr list
# List all PRs regardless of status
aide pr list --status all
# List completed (merged) PRs
aide pr list --status completed
# List your own PRs
aide pr list --created-by "your.email@company.com"
# Combine filters
aide pr list --status active --created-by "john.doe" --limit 10
# Output as JSON for processing
aide pr list --format json
Use Cases
| Goal | Command |
|---|---|
| Find PRs to review | aide pr list --status active |
| Track your work | aide pr list --created-by "me@company.com" |
| Audit merged changes | aide pr list --status completed --limit 50 |
| Monitor team activity | aide pr list --status all |
Best Practices
- Use
--status active(default) for day-to-day review work - Use
--created-byto quickly find your own PRs - Use
--format jsonwhen processing results programmatically - Set
--limithigher when searching for specific PRs
Next Steps
After listing PRs:
- Use pr-view skill to see details of a specific PR
- Use pr-comments skill to check feedback on a PR
- Use pr-diff skill to review code changes
Reply to PR Thread
Reply to an existing comment thread on a pull request.
When to Use
- User wants to respond to specific reviewer feedback
- User wants to continue a discussion in an existing thread
- User wants to acknowledge they've addressed a comment
- User wants to ask follow-up questions in context
How to Execute
Run:
aide pr reply <thread-id> "reply text" [--pr <id>] [options]
Flags
| Flag | Description |
|---|---|
--pr | PR ID or URL (auto-detected from branch if omitted) |
--parent | Parent comment ID for nested replies |
Output Includes
- Thread ID
- Reply content
- Parent comment reference (if specified)
- Timestamp
Common Patterns
# Reply to a thread (auto-detect PR from branch)
aide pr reply 156 "Fixed as suggested in the latest commit"
# Reply to specific PR's thread
aide pr reply 156 "Done, please re-review" --pr 24094
# Reply to specific comment in a thread
aide pr reply 156 "Good point, I've updated the implementation" --parent 789 --pr 24094
Finding Thread IDs
Use the pr-comments skill to load PR comments, which displays thread IDs for each comment thread. Look for the thread ID in the output to use with this command.
Response Patterns
| Scenario | Example Reply |
|---|---|
| Fixed as requested | "Fixed in commit abc123" |
| Explaining approach | "I chose this approach because..." |
| Requesting clarification | "Could you clarify what you mean by...?" |
| Acknowledging feedback | "Good catch! I've updated the implementation" |
| Disagreeing respectfully | "I see your point, but I think X because..." |
Best Practices
- Reply in the relevant thread to keep context together
- Reference commits when changes are made
- Be specific about what was changed
- Ask clarifying questions if feedback is unclear
Next Steps
After replying:
- Use pr-comments skill to see the updated thread
- Use pr-comment skill for new general comments
Update Pull Request
Update an existing pull request's title, description, or status.
When to Use
- User wants to update PR title or description
- User wants to publish a draft PR
- User wants to convert PR back to draft
- User wants to abandon or reactivate a PR
How to Execute
Run:
aide pr update [--pr <id>] [options]
Flags
| Flag | Description |
|---|---|
--pr | PR ID (auto-detected if omitted) |
--title | Update PR title |
--description | Update PR description (alias: --body) |
--target | Change target/base branch |
--draft | Convert to draft PR |
--publish | Publish draft PR (make active) |
--abandon | Abandon the PR |
--activate | Reactivate an abandoned PR |
--tag | Add tag(s) to the PR (repeatable) |
--remove-tag | Remove tag(s) from the PR (repeatable) |
Output Includes
- PR ID and URL
- Updated title and description
- Current status
- Confirmation of changes made
Common Patterns
# Update title (auto-detect PR from branch)
aide pr update --title "PROJ-123: Improved auth flow"
# Update specific PR's description
aide pr update --pr 24094 --description "Updated implementation notes"
# Publish draft when ready for review
aide pr update --pr 24094 --publish
# Convert back to draft if more work needed
aide pr update --pr 24094 --draft
# Abandon PR
aide pr update --pr 24094 --abandon
# Reactivate abandoned PR
aide pr update --pr 24094 --activate
# Add tags
aide pr update --tag bug --tag performance
# Remove tags
aide pr update --remove-tag "old-tag"
# Tag-only update (no other fields needed)
aide pr update --tag "new-tag"
PR Lifecycle Management
| Status | Action | Use Case |
|---|---|---|
| Draft | --publish | Ready for review |
| Active | --draft | Need more work before review |
| Active | --abandon | Close without merging |
| Abandoned | --activate | Reopen previously abandoned PR |
Best Practices
- Update description as implementation evolves
- Publish drafts only when truly ready for review
- Use abandon instead of deleting to preserve history
- Keep title synchronized with actual changes
Next Steps
After updating a PR:
- Use pr-comments skill to check for new feedback
- Use pr-view skill to verify changes
View Pull Request
View details of a pull request including title, description, status, author, and branches.
When to Use
- User asks "what's this PR about?" or "show me the PR"
- User wants context before code review
- User mentions a PR number or asks about current branch's PR
- User needs to understand the scope of changes before diving in
How to Execute
Run:
aide pr view [--pr <id|url>]
- Without
--pr: auto-detects from current branch - With
--pr 123: views specific PR by ID - With
--pr <url>: views PR from Azure DevOps or GitHub URL
Output Includes
- PR number and title
- Status (active, completed, abandoned) and draft state
- Author and creation date
- Source and target branches
- Repository and project
- Description (if present)
Best Practices
- Always check PR status before starting review
- Note draft state - drafts may have incomplete changes
- Check target branch to understand merge destination
- Look for linked tickets in the description
Next Steps
After viewing PR details:
- Use pr-comments skill to see reviewer feedback
- Use pr-diff skill to see code changes
- Use ticket skill to load linked Jira context
Get Sprint Information
Get sprint details for a Jira board, filtered by state.
When to Use
- User asks "what's the current sprint?" or "what sprint are we in?"
- User needs the active sprint ID to search for issues
- User wants to see sprint dates or goals
How to Execute
Run:
aide jira sprint <boardId> [--state active|future|closed] [--format text|json|markdown]
Arguments
| Argument | Description |
|---|---|
boardId | Board ID (from boards command) |
Flags
| Flag | Description |
|---|---|
--state | Sprint state filter (default: active) |
--format | Output format: text, json, markdown |
Examples
# Get active sprint for a board
aide jira sprint 123
# Get future sprints
aide jira sprint 123 --state future
# Get closed sprints
aide jira sprint 123 --state closed
Output Includes
- Sprint ID
- Sprint name
- State (future, active, closed)
- Start and end dates
- Sprint goal (if set)
Common Workflow
To find "what's on the board right now":
- Find the board:
aide jira boards PROJ - Get the active sprint:
aide jira sprint <boardId> - Search for issues in that sprint:
aide jira search "assignee = currentUser()" --sprint-board <boardId>
The --sprint-board flag on the search command combines steps 2 and 3 automatically.
Next Steps
After finding the active sprint:
- Use ticket-search skill with
--sprint-boardto search issues in the sprint - Use ticket skill to view details on specific issues
Manage Ticket Attachments
List, upload, download, or delete attachments on a Jira ticket.
When to Use
- User wants to see what files are attached to a ticket
- User wants to upload a screenshot, log, or document
- User needs to download an attachment for review
- User wants to remove outdated attachments
How to Execute
Run:
aide jira attach TICKET-KEY --<operation> [options]
Operations (one at a time)
| Flag | Short | Description |
|---|---|---|
--list | -l | List all attachments on the ticket |
--upload | -u | Upload file(s) to ticket (can be repeated) |
--download | -d | Download attachment by ID or filename |
--delete | Delete attachment by ID or filename |
Additional Flags
| Flag | Short | Description |
|---|---|---|
--output | -o | Output directory for downloads |
--format | Output format: text, json, markdown |
Output
List mode: Shows attachment details including:
- Filename
- Size
- MIME type
- Author
- Upload date
Upload mode: Confirmation with uploaded file details
Download mode: File saved to current directory or specified output path
Delete mode: Confirmation of deletion
Common Patterns
# List all attachments
aide jira attach PROJ-123 --list
# Upload a single file
aide jira attach PROJ-123 --upload ./screenshot.png
# Upload multiple files
aide jira attach PROJ-123 --upload ./doc1.pdf --upload ./doc2.pdf
# Download by filename
aide jira attach PROJ-123 --download "requirements.docx"
# Download to specific directory
aide jira attach PROJ-123 --download "report.pdf" --output ./downloads
# Delete an attachment
aide jira attach PROJ-123 --delete "old-screenshot.png"
# Get attachment list as JSON
aide jira attach PROJ-123 --list --format json
Workflow
- List first: Always list attachments to see what's available
- Upload supporting files: Add screenshots, logs, or documents
- Download for analysis: Get files locally when needed
- Clean up: Delete outdated or incorrect attachments
Use Cases
| Goal | Command |
|---|---|
| See attached files | aide jira attach PROJ-123 --list |
| Add bug screenshot | aide jira attach PROJ-123 --upload ./bug.png |
| Get attached log | aide jira attach PROJ-123 --download "error.log" |
| Remove old file | aide jira attach PROJ-123 --delete "draft.pdf" |
Best Practices
- List attachments before uploading to avoid duplicates
- Use descriptive filenames when uploading
- Download attachments to review requirements or reproduce issues
- Clean up outdated attachments to keep tickets organized
Next Steps
After managing attachments:
- Use ticket skill to view full ticket details
- Use ticket-comment skill to note attachment changes
Add Ticket Comment
Add a comment to a Jira ticket. Comments support markdown formatting.
When to Use
- User wants to add an update to a ticket
- User wants to ask a question on a ticket
- User wants to document a decision
- User wants to communicate progress or blockers
How to Execute
Run:
aide jira comment TICKET-KEY "comment text" [--format text|json|markdown]
Or read from file:
aide jira comment TICKET-KEY --file ./comment.md
Flags
| Flag | Short | Description |
|---|---|---|
--file | -f | Read comment from markdown file |
--format | Output format: text, json, markdown |
Output Includes
- Comment ID
- Creation timestamp
- Author name
Common Patterns
# Add a simple comment
aide jira comment PROJ-123 "Started working on this task"
# Add a detailed comment with markdown
aide jira comment PROJ-123 "## Progress Update
- Completed initial implementation
- Tests passing locally
- Ready for code review
**Next steps:** Create PR and request review"
# Add comment from file (for longer content)
aide jira comment PROJ-123 --file ./status-update.md
Use Cases
| Purpose | Example |
|---|---|
| Progress update | "Completed initial implementation" |
| Asking questions | "Should this handle edge case X?" |
| Documenting decisions | "Using OAuth 2.0 with PKCE for enhanced security" |
| Communicating blockers | "Blocked on API access - waiting for credentials" |
| Closing notes | "Implementation complete, PR #123 merged" |
Best Practices
- Use markdown for formatted comments (headers, lists, code blocks)
- For long comments, write to a file first and use
--file - Reference other tickets with their keys (e.g., "Related to PROJ-456")
- Include relevant details for future reference
Next Steps
After adding a comment:
- Use ticket-comments skill to see all comments
- Use ticket-transition skill to change status if appropriate
Get Ticket Comments
Retrieve and view comments from a Jira ticket with filtering options.
When to Use
- User asks "what's been discussed on this ticket?"
- User wants to check for updates from stakeholders
- User needs to review feedback or decisions
- User wants to see recent activity on a ticket
How to Execute
Run:
aide jira comments TICKET-KEY [options]
Flags
| Flag | Description |
|---|---|
--author | Filter comments by author name/email |
--since | Show comments since date (YYYY-MM-DD) |
--latest | Show only N most recent comments |
--max-results | Maximum comments to fetch per API call (default: 100) |
--all | Fetch all comments (may require multiple API calls) |
--format | Output format: text, json, markdown |
Output Includes
- Author name
- Timestamp
- Comment content
- Total comment count
Common Patterns
# Get all comments on a ticket
aide jira comments PROJ-123
# Get latest 5 comments
aide jira comments PROJ-123 --latest 5
# Filter by author
aide jira comments PROJ-123 --author "john.doe@company.com"
# Get comments since a date
aide jira comments PROJ-123 --since 2024-01-01
# Combine filters
aide jira comments PROJ-123 --latest 10 --author "reviewer"
# Get all comments with pagination
aide jira comments PROJ-123 --all
# Output as JSON for processing
aide jira comments PROJ-123 --format json
Use Cases
| Goal | Command |
|---|---|
| Review discussion | aide jira comments PROJ-123 |
| Check recent updates | aide jira comments PROJ-123 --latest 5 |
| See specific reviewer | aide jira comments PROJ-123 --author "name" |
| Track since last check | aide jira comments PROJ-123 --since 2024-01-15 |
Best Practices
- Use
--latest Nto focus on recent discussion - Filter by
--authorto see specific stakeholder's input - Use
--sinceto see updates since your last review - Use
--format jsonfor structured processing
Next Steps
After reviewing comments:
- Use ticket-comment skill to respond
- Use ticket-update skill if changes are needed
- Use ticket-transition skill to change status
Create Jira Ticket
Create a new Jira ticket with the specified details.
When to Use
- User says "create a ticket" or "make a new issue"
- User wants to log a bug or create a task
- User needs to track new work in Jira
How to Execute
Run:
aide jira create -p PROJECT -t TYPE -s "Summary" [options]
Required Flags
| Flag | Short | Description |
|---|---|---|
--project | -p | Project key (required, e.g., PROJ) |
--type | -t | Issue type (required, e.g., Task, Bug, Story) |
--summary | -s | Issue summary/title (required) |
Optional Flags
| Flag | Short | Description |
|---|---|---|
--description | -d | Description text in markdown format |
--file | -f | Read description from markdown file |
--assignee | -a | Assignee (email, account ID, or "me") |
--priority | Priority name (e.g., High, Medium) | |
--labels | -l | Labels (comma-separated) |
--component | Component name (can be repeated) | |
--parent | Parent issue key (for subtasks) | |
--field | Custom field (Name=value format) | |
--format | Output format: text, json, markdown |
Custom Fields
The --field flag supports intelligent handling:
- Name resolution: Use
--field "Severity=High"instead of--field "customfield_10269=High" - Auto-formatting: Values are formatted based on field type
- Validation: Invalid values show helpful errors with allowed options
Use ticket-fields skill to discover available fields.
Common Patterns
# Create a simple task
aide jira create -p PROJ -t Task -s "Implement login feature"
# Create a bug with description
aide jira create -p PROJ -t Bug -s "Login fails on Safari" -d "Users report 500 error when logging in"
# Create and assign to yourself with priority
aide jira create -p PROJ -t Task -s "Review PR comments" --assignee me --priority High
# Create with labels and components
aide jira create -p PROJ -t Story -s "User dashboard" --labels "frontend,ux" --component UI
# Create subtask under parent
aide jira create -p PROJ -t Sub-task -s "Write unit tests" --parent PROJ-100
# Create with custom fields
aide jira create -p PROJ -t Bug -s "Critical bug" --field "Severity=Critical"
Output Includes
- Ticket key (e.g., PROJ-123)
- URL to view the ticket
Best Practices
- Use descriptive summaries
- Include enough description for context
- Set appropriate priority
- Use labels for categorization
- Write descriptions in Markdown format
Next Steps
After creating a ticket:
- Use ticket skill to verify details
- Use ticket-update skill to modify fields
- Use ticket-transition skill to change status
Delete Ticket Comment
Delete a comment from a Jira ticket by its comment ID.
When to Use
- User wants to remove a comment they previously added
- User wants to clean up test or draft comments
- User wants to remove outdated or incorrect information
How to Execute
Run:
aide jira delete-comment TICKET-KEY COMMENT-ID [--format text|json|markdown]
Arguments
| Argument | Required | Description |
|---|---|---|
TICKET-KEY | Yes | Jira ticket key (e.g., PROJ-123) |
COMMENT-ID | Yes | ID of the comment to delete |
Flags
| Flag | Description |
|---|---|
--format | Output format: text, json, markdown |
Finding Comment IDs
To find the comment ID you want to delete, first list comments:
aide jira comments PROJ-123 --format json
Each comment in the output will have an id field.
Output Includes
- Confirmation of deletion
- Ticket key
- Deleted comment ID
Common Patterns
# Delete a specific comment
aide jira delete-comment PROJ-123 10001
# Delete with JSON output (useful for scripting)
aide jira delete-comment PROJ-123 10001 --format json
Use Cases
| Purpose | Example |
|---|---|
| Remove test comment | Clean up after testing |
| Remove duplicate | Accidentally posted same comment twice |
| Remove outdated info | Information is no longer accurate |
| Clean up draft | Remove incomplete or draft comment |
Important Notes
- Deletion is permanent and cannot be undone
- You can only delete comments you have permission to delete
- The comment ID is required (use
aide jira commentsto find it)
Next Steps
After deleting a comment:
- Use ticket-comments skill to verify deletion
- Use ticket-comment skill to add a new comment if needed
Edit Ticket Comment
Edit an existing comment on a Jira ticket. Comments support markdown formatting.
When to Use
- User wants to fix a typo or error in a comment
- User wants to add more information to an existing comment
- User wants to update status information in a comment
- User wants to correct inaccurate information
How to Execute
Run:
aide jira edit-comment TICKET-KEY COMMENT-ID "new content" [--format text|json|markdown]
Or read from file:
aide jira edit-comment TICKET-KEY COMMENT-ID --file ./updated-comment.md
Arguments
| Argument | Required | Description |
|---|---|---|
TICKET-KEY | Yes | Jira ticket key (e.g., PROJ-123) |
COMMENT-ID | Yes | ID of the comment to edit |
comment | No* | New comment text in markdown format |
*Either inline comment or --file must be provided.
Flags
| Flag | Short | Description |
|---|---|---|
--file | -f | Read new comment from markdown file |
--format | Output format: text, json, markdown |
Finding Comment IDs
To find the comment ID you want to edit, first list comments:
aide jira comments PROJ-123 --format json
Each comment in the output will have an id field.
Output Includes
- Comment ID
- Updated timestamp
- Author name
Common Patterns
# Edit with inline text
aide jira edit-comment PROJ-123 10001 "Updated comment text"
# Edit with markdown formatting
aide jira edit-comment PROJ-123 10001 "## Updated Status
- Fixed the bug
- Added unit tests
- Ready for review"
# Edit from file (for longer content)
aide jira edit-comment PROJ-123 10001 --file ./updated-comment.md
# Get JSON output
aide jira edit-comment PROJ-123 10001 "Updated" --format json
Use Cases
| Purpose | Example |
|---|---|
| Fix typo | Correct spelling or grammar mistake |
| Add information | Include details that were initially missed |
| Update status | Change "in progress" to "completed" |
| Correct inaccuracy | Fix incorrect technical information |
| Improve formatting | Add markdown headers, lists, or code blocks |
Best Practices
- Use markdown for formatted comments (headers, lists, code blocks)
- For significant changes, write to a file first and use
--file - The entire comment is replaced - include all content you want to keep
- Consider adding an "Updated:" note to indicate the comment was edited
Important Notes
- The edit replaces the entire comment content
- You can only edit comments you have permission to edit
- The comment ID is required (use
aide jira commentsto find it)
Next Steps
After editing a comment:
- Use ticket-comments skill to verify the edit
- Use ticket-delete-comment skill if you need to remove it instead
Discover Jira Fields
Discover what fields are available when creating or updating Jira tickets.
When to Use
- User needs to find correct field names
- User encounters "field not found" errors
- User wants to see allowed values for select fields
- User is preparing to create/update tickets with custom fields
How to Execute
Run:
aide jira fields PROJECT [options]
Options
| Flag | Short | Description |
|---|---|---|
--type | -t | Issue type (e.g., Task, Bug). If omitted, shows all |
--filter | -f | Filter: all, required, optional, custom, system |
--show-values | -v | Display allowed values for select fields |
--max-values | Maximum values to display per field (default: 10) | |
--format | Output format: text, json, markdown |
Common Patterns
# List all fields for a project
aide jira fields PROJ
# List fields for a specific issue type
aide jira fields PROJ -t Bug
# Show only required fields
aide jira fields PROJ -t Task --filter required
# Show custom fields with their allowed values
aide jira fields PROJ -t Bug --filter custom --show-values
# Get full field metadata as JSON
aide jira fields PROJ -t Task --format json --show-values
Integration with Create/Update
Once you discover field names, use them directly with ticket-create or ticket-update:
# 1. Discover available fields
aide jira fields PROJ -t Bug --filter custom --show-values
# Output shows: Severity (customfield_10269) - select
# Values: Critical, High, Medium, Low
# 2. Use the field name (auto-resolved to internal ID)
aide jira create -p PROJ -t Bug -s "My bug" --field "Severity=Critical"
aide jira update PROJ-123 --field "Severity=High"
The --field flag automatically:
- Resolves field names to internal IDs
- Formats values based on field type
- Validates values and shows allowed options on error
Output Includes
- Field name (human-readable)
- Field ID (internal)
- Field type (text, select, array, etc.)
- Whether the field is required
- Allowed values (with
--show-values)
Use Cases
| Goal | Command |
|---|---|
| Find required fields | aide jira fields PROJ -t Bug --filter required |
| See custom fields | aide jira fields PROJ --filter custom |
| Get allowed values | aide jira fields PROJ -t Bug --show-values |
| Get metadata for automation | aide jira fields PROJ --format json |
Best Practices
- Always check fields before creating tickets with custom fields
- Use
--show-valuesto see valid options for select fields - Use
--filter requiredto see mandatory fields - Use
--format jsonfor programmatic access
Next Steps
After discovering fields:
- Use ticket-create skill to create tickets with correct fields
- Use ticket-update skill to update custom fields
Search Jira Tickets
Search for Jira tickets using JQL (Jira Query Language).
When to Use
- User asks "what are my tickets?" or "find tickets about X"
- User wants to search for issues by keyword, status, or assignee
- User needs to query the backlog or sprint
- User wants to find related issues
How to Execute
Run:
aide jira search "JQL query" [maxResults] [--format text|json|markdown]
Flags
| Flag | Description |
|---|---|
maxResults | Maximum results to return (positional, default: 50) |
--limit | Alias for maxResults |
--sprint-board | Board ID to auto-resolve active sprint and prepend to JQL |
--format | Output format: text, json, markdown |
Common JQL Patterns
Personal Queries
# My open tickets
aide jira search "assignee = currentUser() AND status != Closed"
# My in-progress work
aide jira search "assignee = currentUser() AND status = 'In Progress'"
# Tickets I'm watching
aide jira search "watcher = currentUser()"
# Tickets I reported
aide jira search "reporter = currentUser()"
Project Queries
# All open bugs in project
aide jira search "project = PROJ AND issuetype = Bug AND status != Closed"
# High priority unassigned
aide jira search "project = PROJ AND priority = High AND assignee IS EMPTY"
# Sprint tickets
aide jira search "project = PROJ AND sprint in openSprints()"
# Specific component
aide jira search "project = PROJ AND component = 'API'"
Time-Based Queries
# Recent bugs (last 7 days)
aide jira search "issuetype = Bug AND created >= -7d"
# Updated this week
aide jira search "updated >= startOfWeek()"
# Resolved this month
aide jira search "resolved >= startOfMonth()"
Sprint Queries
# Search within active sprint (auto-resolves sprint ID from board)
aide jira search "assignee = currentUser()" --sprint-board 123
# All issues in active sprint
aide jira search "status != Closed" --sprint-board 123
Text Search
# Search by keyword in all text fields
aide jira search "text ~ 'authentication'"
# Search in summary only
aide jira search "summary ~ 'login bug'"
# Combine with filters
aide jira search "project = PROJ AND text ~ 'performance' AND priority = High"
Output Includes
- Ticket key (e.g., PROJ-123)
- Summary/title
- Status
- Assignee
- Priority
Next Steps
After finding tickets:
- Use ticket skill to view full details
- Use ticket-comments skill to see discussion
- Use ticket-update skill to modify tickets
Transition Ticket Status
Change the workflow status of a Jira ticket (e.g., move to "In Progress", "Done").
When to Use
- User wants to start work on a ticket
- User has completed work and wants to close a ticket
- User wants to move a ticket to a different status
- User needs to see available status transitions
How to Execute
List available transitions first:
aide jira transition TICKET-KEY --list
Then transition to desired status:
aide jira transition TICKET-KEY "Status Name" [options]
Flags
| Flag | Short | Description |
|---|---|---|
--list | -l | List available transitions for the ticket |
--comment | -c | Add comment with the transition |
--resolution | -r | Set resolution (for Done/Resolved transitions) |
--format | Output format: text, json, markdown |
Output
When transitioning:
- Confirmation of successful transition
- New status name
- URL to view the ticket
When listing (--list):
- Available transition names
- Target status for each transition
Common Patterns
# List available transitions
aide jira transition PROJ-123 --list
# Move ticket to In Progress
aide jira transition PROJ-123 "In Progress"
# Complete a ticket with comment
aide jira transition PROJ-123 "Done" --comment "Implementation complete, tests passing"
# Resolve with specific resolution
aide jira transition PROJ-123 "Done" --resolution "Fixed"
# Move to code review
aide jira transition PROJ-123 "Code Review"
Common Status Names
Status names vary by project workflow. Common ones include:
| Category | Status Names |
|---|---|
| Not Started | To Do, Open, Backlog |
| In Progress | In Progress, In Development |
| Review | Code Review, In Review, QA |
| Completed | Done, Closed, Resolved |
Best Practices
- Always list available transitions first with
--list - Add comments when transitioning to explain the change
- Set resolution when closing tickets
- Check workflow requirements - some transitions need fields set
Workflow Example
# 1. Start work
aide jira transition PROJ-123 "In Progress" --comment "Starting implementation"
# 2. Move to review
aide jira transition PROJ-123 "Code Review" --comment "PR #456 ready for review"
# 3. Complete work
aide jira transition PROJ-123 "Done" --comment "Merged and deployed" --resolution "Fixed"
Next Steps
After transitioning:
- Use ticket skill to verify the new status
- Use ticket-comment skill to add additional notes
Update Jira Ticket
Update fields on an existing Jira ticket.
When to Use
- User wants to change ticket title or description
- User wants to assign/reassign a ticket
- User wants to change priority or labels
- User wants to update custom fields
How to Execute
First, view the current ticket to see existing values:
aide jira view TICKET-KEY
Then update desired fields:
aide jira update TICKET-KEY [options]
Flags
| Flag | Short | Description |
|---|---|---|
--summary | -s | Update summary/title |
--description | -d | Update description (markdown format) |
--file | -f | Read description from markdown file |
--assignee | -a | Update assignee (email, "me", or "none") |
--priority | Update priority (e.g., High, Medium, Low) | |
--labels | Set labels (comma-separated, replaces existing) | |
--add-labels | Add labels (keeps existing) | |
--remove-labels | Remove specific labels | |
--component | Set components (can be repeated, replaces existing) | |
--field | Custom field (Name=value format) | |
--format | Output format: text, json, markdown |
Custom Fields
The --field flag supports intelligent handling:
- Name resolution: Use
--field "Severity=High"instead of internal IDs - Auto-formatting: Values are formatted based on field type
- Validation: Invalid values show helpful errors
Use ticket-fields skill to discover available fields.
Common Patterns
# Update title
aide jira update PROJ-123 --summary "Updated feature title"
# Update description
aide jira update PROJ-123 --description "New description with **markdown**"
# Update from file
aide jira update PROJ-123 --file ./new-description.md
# Assign to yourself
aide jira update PROJ-123 --assignee me
# Unassign
aide jira update PROJ-123 --assignee none
# Change priority
aide jira update PROJ-123 --priority High
# Add labels without removing existing
aide jira update PROJ-123 --add-labels "needs-review"
# Remove specific labels
aide jira update PROJ-123 --remove-labels "wip,draft"
# Multiple updates at once
aide jira update PROJ-123 --summary "New title" --assignee me --priority High
# Update custom field
aide jira update PROJ-123 --field "Severity=High"
Important Notes
- Description replacement:
--descriptionreplaces the entire description - Description format: Use Markdown - automatically converted to Jira format
- Labels: Use
--labelsto replace all,--add-labelsto add,--remove-labelsto remove - Assignee options: Use "me" for yourself, "none" to unassign, or provide email
Best Practices
- Read the ticket first to preserve existing content when updating description
- Use
--add-labelsinstead of--labelsto avoid removing existing labels - When updating descriptions, preserve important existing content
Next Steps
After updating:
- Use ticket skill to verify changes
- Use ticket-comment skill to note the update
View Jira Ticket
Fetch detailed information about a Jira ticket to understand requirements and context.
When to Use
- User mentions a ticket key (e.g., "PROJ-123")
- User wants to understand a task's requirements
- User asks "what's this ticket about?"
- User is starting work on an issue
How to Execute
Run:
aide jira view <TICKET-KEY> [--format text|json|markdown]
Output Includes
- Summary and description
- Status, priority, type
- Assignee and reporter
- Labels and components
- Created and updated dates
- Any linked issues
Ticket-Driven Development Workflow
Starting Work on a Ticket
- Load ticket context: Use this skill to fetch full details
- Understand requirements: Review description and acceptance criteria
- Check for blockers: Look for linked issues or dependencies
- Review comments: Use ticket-comments skill for discussion history
During Development
- Reference ticket requirements while coding
- Track progress with comments using ticket-comment skill
- Update description if scope changes using ticket-update skill
- Stay aligned by checking for new comments
Completing Work
- Add summary comment documenting what was implemented
- Reference in commits (e.g., "PROJ-123: Add feature")
- Link PR in closing comment
- Transition status using ticket-transition skill
Best Practices
- Always load ticket context before starting implementation
- Keep the ticket updated as you progress
- Use ticket key in commit messages for traceability
- Check comments for clarifications from stakeholders
Next Steps
After loading ticket:
- Use ticket-comments skill to see discussion history
- Use ticket-update skill to modify fields
- Use ticket-transition skill to change status
Hooks 2
Sponsors
Details
- Marketplace
- rlcurrall/aide
- Category
- Community