القائمة
Inspect GitHub pull requests for leadership-relevant release risk, quality gates, ownership, and follow-up actions.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Create, critique, and operationalize engineering strategy documents using diagnosis, tradeoff exploration, guiding policy, coherent actions, and operating cadence. Use when an engineering leader needs strategy for a team, platform, architecture, migration, reliability program, or multi-quarter technical investment.
Run engineering leadership reviews across strategy, delivery, quality, architecture, launch readiness, security risk, and performance health.
Keep dependencies secure, minimal, and up to date. Use when auditing a project's supply chain, adding new libraries, evaluating upgrades, or hardening a CI pipeline against dependency risks.
Design and implement GraphQL APIs with correct schema design, resolver patterns, N+1 prevention, federation, and security. Use when building or evolving a GraphQL layer.
Make ML experiments reproducible and comparable by tracking hyperparameters, metrics, artifacts, and environments. Use when training models, tuning hyperparameters, or promoting models to production.
Ramp up quickly on an unfamiliar codebase by reading strategically, mapping invariants, and making safe first changes. Use when joining a project, reviewing a legacy system, or orienting in a large monorepo.
| name | pr-inspection |
| description | Inspect GitHub pull requests for leadership-relevant release risk, quality gates, ownership, and follow-up actions. |
| license | Apache-2.0 |
| compatibility | Claude Code plugin skill packaged by Agent Packs. |
| metadata | {"agentpacks.version":"0.1.0","agentpacks.source":"https://github.com/agent-packs/registry/tree/main/plugins/github-pr-inspection/.claude-plugin/skills/pr-inspection"} |
Use this workflow when reviewing a pull request from an engineering leadership perspective.
Focus on release risk, customer impact, missing tests, operational readiness, security/privacy exposure, ownership clarity, and whether the change needs broader stakeholder review.
