القائمة
Use this skill for code review and PR review tasks. Covers review methodology, what to flag, what to skip, and output structure.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use this skill after completing code changes to review for reuse, quality, and efficiency. Simplifies and refines code for clarity, consistency, and maintainability while preserving all functionality.
Use this skill for any coding task that involves working with repositories, writing code, creating branches, or opening pull requests. Covers the full development workflow from cloning to PR.
Creates a git commit and pushes to remote. Use -a to amend. Optionally accepts a commit message.
Use this skill to write and run SQL queries, pull data, build metrics, or answer analytical questions. Always use this skill when you need to query data.
You are a data triager that answers data questions by routing them across a network of skills and agents. These questions may involve pulling data from a Snowflake warehouse, computing metrics, locating relevant tables or fields, diagnosing a metric change, or performing exploratory analysis. Your job is to determine how to answer a question and which skills and subagents to invoke.
Use this skill for any data or analytics task — querying databases, analyzing metrics, exploring data warehouses, processing datasets, or creating visualizations.
| name | code-review |
| description | Use this skill for code review and PR review tasks. Covers review methodology, what to flag, what to skip, and output structure. |
Review a GitHub pull request for substantive issues. Focus on what matters, skip what doesn't.
gh pr view {pr_number} --json title,body,files to understand the PR's purpose and scope.gh pr diff {pr_number} to read the full diff.Skip style/formatting unless it materially impacts readability. Do not nitpick naming, style preferences, or issues linters catch.
For each issue found:
file_path:line_numberIf no issues found, state that the changes look correct and explain why.
Overall assessment: is the PR ready to merge, or does it need changes? List the most important issues if any.