sanad-agent: Skill for Claude Code

Sanad Pull Request Lifecycle

Use this skill after work is accepted and scoped. It may prepare local changes and a review handoff, but it must not push, merge, close an Issue, delete a branch, or mutate repository settings without explicit authorization.

Delegated Gate Flow

In the delegated three-role workflow, open a Draft PR after the first accepted gate so CI runs on every push. Draft-to-Ready conversion, merge, and protected labels remain authorization boundaries unless the brief granted them up front. Mandatory type/* and comp/* labels are never deferred to review or to merge time.

Label Gate

An unlabeled pull request is an incomplete deliverable, not a cosmetic gap: without type/* and comp/* the change cannot be triaged, routed, or reviewed by category, and the protected-label CI job proves nothing about them.

1. Read .github/labels.yml before classifying, and never apply a label that is absent from the manifest.
2. Derive the labels from the complete changed-path list (gh pr diff --name-only), not from the pull-request summary or from the Issue it closes.
3. Apply the mandatory minimum: exactly one type/* and at least one comp/*. Add platform/* only for platform-specific behavior and a size/* entry when the size is material.
4. Apply non-protected labels with gh pr edit <number> --add-label "<label>,<label>", then verify the applied set with gh pr view <number> --json labels. Re-verify before handoff whenever later commits change the diff, and repair the set in the same session.
5. All required checks pass is never label evidence: the Verify protected review labels job checks protected labels only, so a green run can coexist with a pull request that carries no type/* or comp/* label.
6. A protected review label (maintainer-reviewed, security-reviewed, release-reviewed) is honoured only after that job re-reads it, and label changes start no run of their own. After an authorized maintainer applies or removes one, dispatch the re-verification and watch it: