ticket-comment
Add a comment to a Jira ticket. Use when the user wants to post an update, ask a question, document a decision, or communicate status on a ticket.
What this skill does
# 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: ```bash aide jira comment TICKET-KEY "comment text" [--format text|json|markdown] ``` Or read from file: ```bash 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 1. Comment ID 2. Creation timestamp 3. Author name ## Common Patterns ```bash # 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
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.