review-pr
Review a pull request against the project's quality standards. Covers the full checklist from the PR review guide — branching, commits, code quality, testing, documentation, and template conventions — and how to provide constructive feedback. Use when reviewing a pull request, checking if a PR meets project standards, or providing feedback on changes. Triggers on "review PR", "review pull request", "check PR", "PR checklist", "code review", or "approve PR".
소스 정보
- 저장소
- torrust/torrust-tracker-deployer
- 최근 소스 활동
- 2026년 2월 25일 19:30
- 감지된 SKILL.md 언어
- 영어
- 스타
- 5
- 포크
- 2
설치 방법
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
소스 파일 검토
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
SKILL.md 표시 중
SKILL.md
소스 지침 · 읽기 전용 미리보기- name
- review-pr
- description
- Review a pull request against the project's quality standards. Covers the full checklist from the PR review guide — branching, commits, code quality, testing, documentation, and template conventions — and how to provide constructive feedback. Use when reviewing a pull request, checking if a PR meets project standards, or providing feedback on changes. Triggers on "review PR", "review pull request", "check PR", "PR checklist", "code review", or "approve PR".
- metadata
- {"author":"torrust","version":"1.0"}
# Review a Pull Request
## Process
1. **Read the PR review guide** — [`docs/contributing/pr-review-guide.md`](../../docs/contributing/pr-review-guide.md) is the single source of truth. Do not rely on your general knowledge; follow the checklist there.
2. **Work through each checklist item** in the guide against the actual changes in the PR:
- Branching & Commits
- Code Quality (DDD layers, error handling, module organization)
- Testing
- Documentation
- Templates (if applicable)
3. **Check the Quick Red Flags section** — scan the diff for the listed architecture violations, error handling issues, code organization problems, and testing issues.
4. **Distinguish expected from real errors** — consult [`docs/contributing/known-issues.md`](../../docs/contributing/known-issues.md) before flagging anything as a problem.
5. **Provide feedback** following the guide's conventions:
- **Request Changes** for blocking violations of documented standards
- **Comment** for non-blocking suggestions
- **Approve** only when all checklist items are satisfied
> The guide has examples of good vs. better feedback with specific references to documentation and line numbers. Follow that pattern.
GitHub에서 보기