ticket-delete-comment

Included with Lifetime

$97 forever

Delete a comment from a Jira ticket. Use when the user wants to remove a comment they previously added or clean up outdated comments.

General

What this skill does


# 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:

```bash
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:

```bash
aide jira comments PROJ-123 --format json
```

Each comment in the output will have an `id` field.

## Output Includes

1. Confirmation of deletion
2. Ticket key
3. Deleted comment ID

## Common Patterns

```bash
# 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 comments` to 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

Files: 1

Size: 2.2 KB

Complexity: 10/100

Category: General

Source: https://github.com/rlcurrall/aide/tree/main/skills/ticket-delete-comment

Related in General

modeling-omnistudio-epc-catalog

Included

Salesforce 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).

Generalscripts

relationship-science-coach

Included

Use 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.

Generalscripts

building-sf-integrations

Included

Salesforce 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).

Generalscripts

venue-templates

Included

Access 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.

Generalscripts

let-fate-decide

Included

Draws 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.

Generalscripts

net-ops

Included

Cross-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.

Generalscripts