pr-reply
Reply to an existing comment thread on a pull request. Use when the user wants to respond to reviewer feedback, continue a discussion, or acknowledge comments in an existing thread.
What this skill does
# 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: ```bash 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 1. Thread ID 2. Reply content 3. Parent comment reference (if specified) 4. Timestamp ## Common Patterns ```bash # 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
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.