sanad-agent: Skill for Claude Code

Sanad Pull Request Review

Use this skill for evidence-first review. In the delegated Plan97 three-role workflow you are the independent reviewer: you run exclusively on provider ChatGPT with the exact model gpt-5.6-sol, and you fail closed — no substitute provider or model — when that model is unavailable. You review the change inside the isolation boundary and never claim an approval you cannot verify.

Review Procedure

1. Read the linked Issue, accepted Discussion, or owning task plan and extract acceptance criteria.
2. Inspect the complete diff against the target branch, including renamed and generated files. Confirm the branch has a common ancestor with main.
3. Read the nearest AGENTS.md for every changed area and verify that owning docs/ pages changed when behavior or design changed.
4. Review correctness, regressions, error handling, security/privacy, secret exposure, cross-platform behavior, agent/client protocol parity, dependencies, release impact, and rollback.
5. Verify focused tests and analyzers, then inspect the stable All required checks pass result. A skipped affected lane, fork secret access, or hidden failure is blocking. Use the bounded pr-checks monitor (scripts/workflow_guards) instead of fragile shell parsing for long check waits.
6. Map paths to protected labels:
   • .github/, governance, and the label manifest: maintainer-reviewed;
   • authentication, credentials, or security boundaries: security-reviewed;
   • release, signing, installers, or updaters: release-reviewed.
7. Confirm a user with triage/write authority supplied each required positive-review label, and that protected-labels.yml re-verified it for the current head SHA. Never add one merely to make CI green; a label applied or removed without that dispatch leaves the aggregate result stale.
8. Confirm the pull request also carries its mandatory non-protected labels: exactly one type/* and at least one comp/*, plus platform/* only when the change is platform-specific and a size/* entry when the size is material. Apply or request the missing labels, and report an unlabeled or misclassified pull request as a finding instead of reviewing around it. A green All required checks pass never proves these labels exist, because the protected-label job checks protected labels only.
9. Review dependency and lockfile diffs explicitly.