Como usar
- Copie o comando e verifique o pacote antes de instalar no seu ambiente de agente.
- Consulte no original as ferramentas, credenciais e ambientes necessários.
- Descreva os dados de entrada e a entrega esperada; confira a saída com as fontes.
npx skills add https://github.com/cryskai/crysk --skill crysk-prAntes de começar
- A instalação não inclui assinatura de modelo, franquia API ou acesso aos seus arquivos.
- Estrelas e instalações indicam atividade, não um teste independente de qualidade ou segurança.
Renderizado do repositório de origem, preservando títulos, exemplos, código, tabelas, links e imagens.
When to Use
Load this skill whenever the user asks to open, create, submit, or update a pull request (or push a branch and open a PR).
Step 1: Branch, Pre-Push Checks & Repo Conventions
- Protect integration branches: Never commit or push directly to the default branch, or to the integration branch the repository declares (for example
devin a repo whose rules say so). If currently on one, create a focused branch first (feat/<slug>,fix/<slug>,chore/<slug>,refactor/<slug>). - Resolve target base branch:
- Check
AGENTS.md,CLAUDE.md,CONTRIBUTING.md, or an active project PR skill (such asbranch-prorgh-stack) for the required target branch (e.g.devvsmain). - If the repo defines no rule, inspect whether an active
devintegration branch exists or fall back togh repo view --json defaultBranchRef --jq .defaultBranchRef.name.
- Run local gates before pushing: Run the project's fast verification commands (tests, typecheck, linter) before pushing the branch (
git push -u origin HEAD).
Step 2: PR Title & Description (Repo Template or Built-in Fallback)
- Check repo rules first:
- If the repository has
.github/pull_request_template.md,.github/PULL_REQUEST_TEMPLATE/, or instructions inAGENTS.md/CONTRIBUTING.md/ an active PR skill, follow that structure.
- Fallback template (when the repository has no PR template or rules):
- Never rely on a bare
gh pr create --filldump. - Title: Conventional Commit format (
<type>(<scope>): <imperative summary>, max 72 chars), stating what changed clearly. - Body: Pass via
--body-file(or a quoted heredoc) using this structure:
## Summary
- **What & Why:** 1–3 concise bullets explaining the problem solved or capability added and why it was needed.
## Key Changes
- `<path/or/module>` — what changed and any non-obvious design or tradeoff decision.
## Verification
- Exact local commands executed (`test`, `typecheck`, `lint`) and their results.
## Related Issues
- `Closes #<id>` / `Refs #<id>` (or `None`).- Attribution lines (
Co-Authored-By, generated-by footers) follow the repository's rules and the user's own instructions; this skill adds none and removes none.
- Create (or locate) the PR:
- Run
gh pr create --base <base> --title "<title>" --body-file <file>(orgh pr view --json number,urlif a PR for the current branch is already open and you just pushed new commits). - Capture the pull request number
<n>.
Step 3: Auto-Subscribe to crysk & Enter the Triage Loop (No Human Friction)
Check whether the repository uses Crysk (e.g., .github/workflows/crysk.yml (pr-hero.yml before the rename) or .crysk/ (.prhero/ before the rename) exists in the repo, or crysk (pr-hero before the rename) status checks run on PRs). If not, report the PR URL and stop.
When crysk is active on the repository, never stop right after `gh pr create`. Immediately continue in the same turn:
- Subscribe to the initial review from second zero:
npx -y crysk status --pr <n> --wait --json--wait holds automatically during the 3-minute startup grace window while gate.state is "none" (waiting for GitHub Actions to pick up the new PR), continues polling every 15s while gate.state is "pending", and returns as soon as the review settles.
- Route on `next_action`:
- `next_action === "done"`: First, if
findingslists rows withcomment_id: null(thereasonsays they "live only in the summary comment"), read each one in the PR's summary comment: an outside-diff finding has no thread, sodonedoes not mean it was answered. Fix the real ones or hand off tocrysk-loop; never report the PR ready without naming them. Then check whetherreport.headis non-null andreport.head !== head(a green status carried forward over an unreviewed push underonce_per_pr,thresholded, orrisk_aware). If so andgit diff <report.head>..<head>contains non-trivial logic or risky changes, explicitly recommend running/crysk reviewto the user naming those changes. Otherwise, the review passed the gate with zero untriaged findings: report the PR URL and clean review summary to the user. - `next_action !== "done"` (`"triage"`, `"fix"`, `"recheck"`, `"review"`, `"override-or-fix"`):
Immediately load the crysk-loop skill (skills/crysk-loop/SKILL.md) and run its autonomous loop (while (next_action !== "done")) to judge findings, reply, push verified fixes, and wait for re-review until the PR is ready to merge.