Automated summary
Displays details of a pull request such as title, status, author, branches, and description.
Strengths
- Quick overview without leaving terminal
- Auto-detects PR from current branch
- Provides status and draft state for context
Limitations
- Depends on Azure DevOps integration
- Limited to viewing; no interactive filtering
When you need a summary of a PR before reviewing code or understanding its scope.
When you need to see the actual code changes or comments within the PR.
Security analysis
SafeThe skill only invokes a read-only CLI command (aide pr view) to display pull request details. No destructive, exfiltrating, or obfuscated actions are present. The use of Bash is limited to a safe, specific command.
No concerns found
How this analysis is madeExamples
Show me the PR for this branchView PR 42Show details of https://dev.azure.com/org/project/_git/repo/pullrequest/123name: pr-view description: View pull request details including title, status, branches, and description. Use when the user asks about a PR, wants PR context, mentions viewing/checking a pull request, or needs to understand what a PR is about. allowed-tools: Bash(aide:*)
View Pull Request
View details of a pull request including title, description, status, author, and branches.
When to Use
- User asks "what's this PR about?" or "show me the PR"
- User wants context before code review
- User mentions a PR number or asks about current branch's PR
- User needs to understand the scope of changes before diving in
How to Execute
Run:
aide pr view [--pr <id|url>]
- Without
--pr: auto-detects from current branch - With
--pr 123: views specific PR by ID - With
--pr <url>: views PR from Azure DevOps URL
Output Includes
- PR number and title
- Status (active, completed, abandoned) and draft state
- Author and creation date
- Source and target branches
- Repository and project
- Description (if present)
Best Practices
- Always check PR status before starting review
- Note draft state - drafts may have incomplete changes
- Check target branch to understand merge destination
- Look for linked tickets in the description
Next Steps
After viewing PR details:
- Use pr-comments skill to see reviewer feedback
- Use pr-diff skill to see code changes
- Use ticket skill to load linked Jira context
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/view-pull-request-details-mm78nn0x/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/view-pull-request-details-mm78nn0x' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/view-pull-request-details-mm78nn0x/download' --output '.skill-downloads/view-pull-request-details-mm78nn0x/SKILL.md.part' && mv '.skill-downloads/view-pull-request-details-mm78nn0x/SKILL.md.part' '.skill-downloads/view-pull-request-details-mm78nn0x/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/view-pull-request-details-mm78nn0x/SKILL.md' && test -s '.skill-downloads/view-pull-request-details-mm78nn0x/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/pr-view' && cp -R '.skill-downloads/view-pull-request-details-mm78nn0x' '.claude/skills/pr-view'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/view-pull-request-details-mm78nn0x'openskills read 'view-pull-request-details-mm78nn0x'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/view-pull-request-details-mm78nn0x/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.