ticket-comments
Get comments from a Jira ticket to review discussion history. Use when the user wants to see ticket comments, check for updates, review feedback, or understand the discussion on an issue.
What this skill does
# 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: ```bash 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 1. Author name 2. Timestamp 3. Comment content 4. Total comment count ## Common Patterns ```bash # 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 "[email protected]" # 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 N` to focus on recent discussion - Filter by `--author` to see specific stakeholder's input - Use `--since` to see updates since your last review - Use `--format json` for 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
Related in Code Review
gstack
IncludedFast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)
startup-due-diligence
IncludedLegal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.
interview-master
IncludedThis skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.
fix-issue
IncludedFixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.
sf-apex
IncludedGenerates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.
swift-development
IncludedComprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.