Notre avis
Publie un commentaire sur une pull request, soit général, soit sur un fichier ou une ligne spécifique.
Points forts
- Supporte les commentaires généraux et en ligne.
- Détecte automatiquement la PR à partir de la branche.
- Permet de commenter des fichiers et lignes spécifiques.
- Utile pour demander une relecture ou documenter des décisions.
Limites
- Nécessite un dépôt Git configuré avec un remote.
- Ne permet que l'ajout de commentaires, pas la modification ou la suppression.
- La sortie se limite à l'ID du thread et au contenu, sans réponse au thread.
Utilisez pour ajouter des retours, demander une relecture ou documenter des décisions sur une pull request.
Ne pas utiliser pour une discussion de code approfondie qui serait mieux traitée par un outil de revue de code dédié.
Analyse de sécurité
SûrThe skill runs a single, fixed command 'aide pr comment' with user-provided arguments. It does not execute arbitrary shell commands, access sensitive files, or expose secrets. There is no risk of destructive or exfiltrating actions.
Aucun point d'attention détecté
Exemples
Post a comment on the current PR saying 'Ready for re-review after addressing all feedback'.Add a comment to PR #24094 on file src/auth.ts: 'Consider refactoring this section'.Comment on line 127 of src/utils/helpers.ts in the current PR: 'Added null check as suggested'.name: pr-comment description: Post a comment on a pull request. Use when the user wants to add a comment to a PR, respond to feedback, request review, or document decisions. allowed-tools: Bash(aide:*)
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
Expert Next.js App Router
Developpement
Un skill qui transforme Claude en expert Next.js App Router.
Générateur de README
Developpement
Crée des README.md professionnels et complets pour vos projets.
Rédacteur de Documentation API
Developpement
Génère de la documentation API complète au format OpenAPI/Swagger.