Loading...
Loading...
Found 207 Skills
Philosophy-aware PR reviews checking alignment with amplihack principles. Use when reviewing PRs to ensure ruthless simplicity, modular design, and zero-BS implementation. Suggests simplifications, identifies over-engineering, verifies brick module structure. Posts detailed, constructive review comments with specific file:line references.
View and manage inline GitHub PR review comments with full thread context from the terminal
This skill is used when users request phrases such as 'handle PR review issues', 'fix review items', 'resolve PR feedback', 'process review issues one by one', 'complete review tasks', 'run pr review resolver', 'resolve PR review', 'address review comments', 'fix review findings', or 'handle code review'. It reads the review comments of the PR associated with the current branch, discusses each unresolved issue with the user one by one, lets the user decide on the handling approach, and executes fixes in parallel as background subtasks.
Review PyTorch pull requests for code quality, test coverage, security, and backward compatibility. Use when reviewing PRs, when asked to review code changes, or when the user mentions "review PR", "code review", or "check this PR".
Review the current Pull Request that has been checked out locally with structured feedback on code quality, issues, testing, and suggestions. Use when you need a comprehensive code review of a PR branch.
Fetch PR feedback from all GitHub sources and validate every comment before acting. Use when user needs to process PR review comments, address reviewer feedback, or triage pull request discussions. Use for "review comments", "PR feedback", "address reviews", "address feedback", or "what did reviewers say". Do NOT use for creating new PRs, code review of local changes, or general code analysis without an existing PR.
Human reviewer self-review for backend PRs — naming, complexity, DB schema, test design, type precision. Use when user says "review my PR", "check my PR", "human review", or wants design/readability feedback. Applies to any TypeScript backend; pair with pr-review-frontend for full-stack PRs.
Submit pull request (PR) review from chat session to PR conversations. Use when asked to "submit PR review" or "submit review to PR #123". Identifies issues in the current chat session, creates line-specific review comments, avoids duplication with existing comments, and submits the review via GitHub CLI.
This skill should be used when the user asks to "review PR and save results", "run PR review with documentation", "create PR review document", "review and document PR", "save PR review to docs", "document PR review", or mentions reviewing a PR with the intention of saving the review results. Executes comprehensive PR review using pr-review-toolkit with opus model and posts results as a PR comment.
Trigger this skill when the user wants to start an asynchronous PR review, run background checks on a PR, or check the status of a previously started async PR review.
Use when the user asks to review pull requests, analyze code changes, check for security issues in PRs, or assess code quality of diffs.
Analyze and explain a pull request to help review it effectively