Automated summary
Posts a comment on a pull request, either general or inline on a specific file/line.
Strengths
- Supports general and line-specific comments.
- Auto-detects PR from branch.
- Allows commenting on specific files and lines.
- Useful for requesting re-review or documenting decisions.
Limitations
- Requires a configured Git repository with remote.
- Only supports comment posting, not editing or deleting.
- Output is limited to thread ID and content, no reply threading.
Use to add feedback, request re-review, or document decisions on a pull request.
Do not use for extensive code discussion that would be better served by a dedicated code review tool.
Security analysis
SafeThe 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.
No concerns found
How this analysis is madeExamples
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
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/post-pr-comment-mmh8qqcz/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/post-pr-comment-mmh8qqcz' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/post-pr-comment-mmh8qqcz/download' --output '.skill-downloads/post-pr-comment-mmh8qqcz/SKILL.md.part' && mv '.skill-downloads/post-pr-comment-mmh8qqcz/SKILL.md.part' '.skill-downloads/post-pr-comment-mmh8qqcz/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
Tools declared by the author (check availability in your agent): Bash(aide:*)
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/post-pr-comment-mmh8qqcz/SKILL.md' && test -s '.skill-downloads/post-pr-comment-mmh8qqcz/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/pr-comment' && cp -R '.skill-downloads/post-pr-comment-mmh8qqcz' '.claude/skills/pr-comment'Cursor
test -f '.skill-downloads/post-pr-comment-mmh8qqcz/SKILL.md' && test -s '.skill-downloads/post-pr-comment-mmh8qqcz/SKILL.md' && mkdir -p '.cursor/skills' && test ! -e '.cursor/skills/pr-comment' && cp -R '.skill-downloads/post-pr-comment-mmh8qqcz' '.cursor/skills/pr-comment'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/post-pr-comment-mmh8qqcz'openskills read 'post-pr-comment-mmh8qqcz'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/post-pr-comment-mmh8qqcz/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.