sanad-agent: Skill for Claude Code

Sanad Pull Request Review

Use this skill for evidence-first review. It reports findings but does not approve, merge, add protected labels, or perform another maintainer action without explicit authorization.

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.
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. Never add one merely to make CI green.
8. Review dependency and lockfile diffs explicitly.

Findings Format

Order findings by severity:

• Blocker: unsafe, incorrect, acceptance-breaking, secret-exposing, or required evidence missing.
• Warning: material risk or maintainability problem that should be resolved before merge.
• Suggestion: non-blocking improvement.

Each finding includes a precise path/location, impact, evidence, and actionable correction. If no finding remains, state the residual risks and exact verification reviewed. Do not claim approval for a security-sensitive change solely because this skill produced no findings.

Mutation Boundary