cryskai/crysk

crysk-ci-setup

Trigger: setup CI, add Crysk to CI, GitHub Actions review, CRYSK secrets, crysk-secrets, CRYSKMODELS, models per role in CI, OpenCode, DeepSeek, CRYSK-INPUT-REMOVED, old OPENCODEAUTHJSON / CRYSKROUTING workflows, admission policy, configure CI workflow, ret…

ソースを見る

使い方

  1. インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
  2. 必要なツール、認証情報、対応環境を原文で確認します。
  3. 入力と成果物を指定し、出力を資料と照合します。
npx skills add https://github.com/cryskai/crysk --skill crysk-ci-setup

開始前の確認

  • 導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
  • スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
リポジトリの原文

見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。

Activation Contract

Load when the user asks to:

  • Add Crysk to GitHub Actions CI, scaffold .github/workflows/crysk.yml, or configure secrets. No local install is needed: the workflow file is the whole install.
  • Configure the models per role in CI, or OpenCode (CRYSK_MODELS, CRYSK_OPENCODE_* secrets, DeepSeek, mixed Claude+OpenCode, fallbacks).
  • Move a workflow off the removed inputs (CRYSK-INPUT-REMOVED: claude-token, anthropic-api-key, opencode-auth with the OPENCODE_AUTH_JSON secret, routing with the CRYSK_ROUTING variable).
  • Tune CI spend / re-review / admission policy.
  • Retrigger a skipped CI review (size, admission, or budget) without running the review locally.
  • Reduce review noise: fewer comments (post_min_severity) or fewer blocking findings that are real but improbable (materiality_gate).

Hard Rules

  • Zero secret leakage: NEVER print, cat, commit, or log API keys, tokens, or an OpenCode auth.json record. Reference ${{ secrets.* }} names only. Inspect auth.json keys and `type` only.
  • One `CRYSK_ secret per credential, nothing else:** CRYSKCLAUDEOAUTHTOKEN` (subscription), `CRYSKCLAUDEAPIKEY, CRYSKOPENCODE<P>APIKEY per OpenCode provider, CRYSKOPENCODEOPENAIOAUTH` for an OpenAI subscription. The workflow names each one in its `crysk-secrets` block, never `toJSON(secrets)`. The old `CLAUDECODEOAUTHTOKEN, ANTHROPICAPIKEY and OPENCODEAUTHJSON secrets and the CRYSKROUTING` variable are read by nothing. Models per role go in the public variable `CRYSKMODELS (no credentials in it), the Claude order in CRYSKCREDENTIALS`, the OpenCode providers in `CRYSKOPENCODE_PROVIDERS`.
  • No install needed: run every Crysk command as npx -y crysk <command> (Node is enough; the package brings its own Bun). A global crysk on PATH is the same command. CI itself needs no local CLI at all: the workflow runs the action. npx -y crysk skills install installs the Crysk, triage, and CI-setup skills into every detected coding agent, with no TTY and no MCP or launchd registration (neither is needed for the CI loop, and npx's temporary cache refuses them).
  • Deterministic scaffolding: Run npx -y crysk setup --ci (or npx -y crysk ci init) with the interview's flags. It writes the one workflow file, .github/workflows/crysk.yml (a repo that already has pr-hero.yml keeps it: --force rewrites it in place, and setup refuses to add a second file beside it). Do not fabricate it from memory. Fallback: copy assets/workflow.yml. Never scaffold a pr-hero-force.yml; it is retired.
  • `fetch-depth: 0` is mandatory on actions/checkout@v4.
  • Gate mode: the crysk commit status is the required check (the legacy pr-hero status is no longer posted). The scaffold writes mode: gate explicitly: blocking findings, a size or spend-ceiling skip, and a crash set it red. Every review rule that skips a push (low-risk delta, once per PR, /crysk stop, the attempt budget used up, manual_only) carries the last verdict; answered blocking findings turn a carried red green, marked unverified. Under the attempt budget used up or manual_only, that green is held pending instead, so a push past the budget or under manual_only never turns green without a /crysk review or a /crysk override. mode: advisory keeps it green for a finished review. The job's exit code stays 0 on findings either way, so do not gate on the job.
  • Required permissions: contents: read, pull-requests: write, issues: write, statuses: write, `checks: write`, `actions: read` (the admission gate lists past runs; a private repo 403s without it). Template in assets/workflow.yml includes all six.
  • Retrigger is a PR comment: `gh pr comment <n> --body "/crysk review"`. GitHub Actions runs the review on the runner with --force. The comment must be exactly /crysk review (or /crysk review --full; /pr-hero review on a workflow scaffolded before the rename, see the /crysk vs /pr-hero bullet), and its author needs write access; the action refuses anyone else. Do not run crysk review --force locally when the review should happen in CI. gh run rerun on a skipped run re-evaluates the gates and does not force. In this repo a comment run checks out the PR head commit before uses: ./, so it runs the PR's own engine, not the default branch's.
  • `/crysk recheck` re-reviews the head and asks the CI adjudicator to rule on pending dismissals. It is /crysk review plus --adjudicate, with the same permission check and reaction; refused on fork pull requests. See docs/github-actions.md ("Rechecking a dismissal").
  • `/crysk stop` stops automatic reviews on the PR. Post it before a push that should not be reviewed: CI admission skips every later automatic review, carrying the last verdict, until a /crysk review or /crysk recheck comment. It counts only from a user with write access (checked at admission), starts no run, and never turns the gate green. See docs/github-actions.md ("Stopping automatic reviews").
  • `--force` never widens discovery; `--full` does. When a prior review of the same head was hollow or wrong and re-runs report "No changes to discover", comment /crysk review --full. It passes --full, which re-discovers the whole PR range.
  • When the comment trigger takes effect: GitHub reads a comment-triggered workflow from the default branch (for this repo, main, not dev), so /crysk review works only once the workflow file (crysk.yml, or pr-hero.yml in a repo set up before the rename) with its issue_comment trigger is merged there; a user repo also needs an action release that handles the comment, through the @v0 it pins.
  • `/crysk` vs `/pr-hero`: the commands are /crysk review, /crysk recheck, /crysk override and /crysk stop; the action still accepts /pr-hero … for one version. A pr-hero.yml scaffolded before the rename filters only /pr-hero …, so a /crysk … comment starts nothing there: re-run npx -y crysk ci init --force to accept both, which also moves the workflow to the CRYSK_* secrets.
  • Legacy scaffolds: a pr-hero.yml scaffolded before the comment trigger has no issue_comment listener, so a comment does nothing. There, use gh workflow run pr-hero-force.yml -f pr=<n> (add -f full=true to re-discover), or re-scaffold with npx -y crysk ci init --force, which leaves pr-hero-force.yml in place.
  • Minimum action version: this workflow listens to comments, and only an action release that ships the comment handling checks the command and the commenter's write access. An older action reviews on ANY comment starting with /crysk review, from anyone who can comment. Never pair this workflow with an older action; a pinned tag or sha must be at or after that release.
  • Older heads (this repo): a comment run loads the PR head's own action.yml, so on a head from before the comment handling it reviews without reading the comment (no force, no --full); merge or rebase the PR onto a base that has it first.
  • Trust (this repo): a comment run runs the PR head's code, including its bun install, with the workflow's secrets, so write access is checked twice: by the workflow's pre-checkout step (fail closed, before any head code runs) and again by the head's action.yml.
  • Admission config is repo-level: Write .crysk/config.json on the default branch. That file rejects models and credentials: they are person-layer only ($HOME/.crysk/config.json on the runner, written from vars.CRYSK_MODELS and vars.CRYSK_CREDENTIALS).
  • `.cryskignore` is read from the base ref, not the PR branch, in CI.
  • Models and OpenCode are DATA: the scaffold passes models: ${{ vars.CRYSK_MODELS }}, credentials: ${{ vars.CRYSK_CREDENTIALS }} and five OpenCode slot lines driven by vars.CRYSK_OPENCODE_PROVIDERS. Unset CRYSK_MODELS = Claude CI. Never a per-provider Action input. A repository connected to the Crysk platform takes its models from the platform, which wins over the inputs.
  • OpenCode procedure: when OpenCode or mixed backends are in scope, follow references/opencode-ci.md before setting GitHub DATA (roles, model names, one secret per provider, the providers variable).

Decision Gates

ConditionAction
gh auth status succeedsOffer gh secret set / gh variable set
gh missing/unauthenticatedLink to repo Settings → Secrets and variables → Actions (Variables tab for CRYSK_MODELS, CRYSK_CREDENTIALS, CRYSK_OPENCODE_PROVIDERS)
Credential: Claude`CRYSK_CLAUDE_OAUTH_TOKEN` — subscription (claude setup-token only, NOT keychain). `CRYSK_CLAUDE_API_KEY` — pay-as-you-go. Both set: the subscription runs unless CRYSK_CREDENTIALS is {"claude": ["api_key", "subscription"]}.
Credential: OpenCodeRead references/opencode-ci.md. One CRYSK_OPENCODE_<P>_API_KEY per provider + CRYSK_MODELS + CRYSK_OPENCODE_PROVIDERS. Any CRYSK_* credential counts; with none, the run fails red with the gh secret set commands.
openai in CICRYSK_OPENCODE_OPENAI_API_KEY runs metered; CRYSK_OPENCODE_OPENAI_OAUTH (base64 of the openai record of OpenCode's auth.json) is the ChatGPT subscription and wins when both are set. _OAUTH works for openai only.
Workflow red with CRYSK-INPUT-REMOVEDIt still passes claude-token, anthropic-api-key, opencode-auth or routing. npx -y crysk ci init --force, then set the CRYSK_* secrets and variables it prints.
Different models per stepCRYSK_MODELS maps roles to lists: default, hunter.<key>, refuter, consolidate, scout, summary, judge. Any role left on a claude: model needs a Claude secret; OpenCode-only = every role on OpenCode, e.g. {"default": ["opencode:deepseek/deepseek-v4-flash"]} (references/opencode-ci.md).
Several OpenCode providers in one runSupported: up to 5 providers through the workflow's slots, each model on its own provider's secret, as primary or fallback.
OpenCode CLI pinAction installs 1.18.30 iff the setup step wrote an OpenCode auth file OR the models in effect name opencode:. Never latest.
Fork PRsTheir pushes skip (no secrets). A user with write access comments /crysk review, and that run (base context, with secrets) reviews the fork head. Review if never reads secrets; the action checks for a CRYSK_* credential in crysk-secrets (or a login file already on the runner).
Spend gatesDefaults: budget-usd: 10.00 on metered routes (the run chose CRYSK_CLAUDE_API_KEY, or an OpenCode auth file was built), max-changed-lines: 4000 and max-changed-files: 50 on metered routes only; a Claude subscription route has no size limit unless the workflow or .crysk/config.json sets one. A subscription run stays unlimited unless an OpenCode auth file is also present.
Existing workflowsetup --ci skips; ask before --force
First-time admissionRecommend ci_admission_observe_only: true — references/ci-admission.md
User wants max CI spendLower ci_max_attempts and/or raise ci_rereview_min_score
Custom bot posts findingsAdd login to ci_trusted_actors
Too many advisory comments on PRsRaise the posting floor: post_min_severity: "blocking" in .crysk/config.json posts only blocking findings ("warning", the recommended floor setup writes, hides advisory suggestions only). Blocking findings always post; the gate is unchanged.
Blocking findings that are real but improbable keep PRs red ("an edge case that never happens")Offer materiality_gate: true in .crysk/config.json (opt-in, off by default). An isolated judge checks each blocking finding against Crysk's posting policy; one judged not material under normal use posts as advisory and does not block. Security, credential and data-loss findings are never demoted, and any judge failure keeps the finding blocking. Cost: one sonnet call per blocking finding (about 1 per PR, roughly +$0.015 notional and +10 s per review). Pair it with post_min_severity: "blocking" to hide the demoted ones entirely.
materiality_gate is on but nothing is ever demotedRead the materiality record in the run's pipeline.json (in the crysk-run-* artifact). unsupported_route: the judge runs only on claude:sonnet-latest or claude:opus-latest, so a models.judge in CRYSK_MODELS that lists neither stands it down; remove that role or list one of the two. ceiling: the pipeline ceiling left no room for one judge wave (about 9 minutes). ran with judged: 0: the run had no blocking finding the safety guard leaves unprotected, so there was nothing to judge. skipped on a re-review with no new commits to review is expected (the judge is left out when nothing new is hunted). skipped anywhere else means the key did not reach the run: the repo config must be on the PR's base branch (CI reads it from there) and a global config must not set it false (the key is capped).
CI skipped (size, admission, or budget)gh pr comment <n> --body "/crysk review". The review runs on GitHub Actions. Do not run crysk review --force locally for this. Legacy scaffold (no issue_comment trigger): gh workflow run pr-hero-force.yml -f pr=<n>.
Gate is red with blocking findings the team acceptsgh pr comment <n> --body "/crysk override" (write access, same-repo PRs only, valid for that head only; a same-head /crysk review keeps it red).
Prior review of the same head was hollow or wrong; re-runs say "No changes to discover"gh pr comment <n> --body "/crysk review --full". A plain /crysk review keeps the narrowed discovery.
Gate red: crysk: review partial (N of M hunters failed, set abc123) — /pr-hero review retries itSome hunters failed and nothing blocking was found. gh pr comment <n> --body "/crysk review". If the same hunters fail every run, fix their route (model, credential) or override.
Gate red: crysk: review partial again (N of M hunters failed, set abc123) — fix the failing route or /pr-hero overrideThe previous review of this head was partial with the same hunters failing, so a retry already failed the same way. Fix the failing hunter's route (model, credential), or gh pr comment <n> --body "/crysk override". crysk status answers override-or-fix.
Gate error: CRYSK-CANCELLED: not reviewed — /pr-hero review reviews this headThe review run was cancelled (a newer push, or by hand). Comment /crysk review to review the head.
CRYSK-MODEL-UNAVAILABLE (lead "Provider <name>:")Every hunter's route names a model the provider does not serve. Fix the model id in CRYSK_MODELS (check opencode models <provider>).
CRYSK-CRED-UNUSABLE ("The route <provider>/<model> has no usable credential record")No CRYSK_OPENCODE_<P>_API_KEY reached the run for that provider: set it, add its token to CRYSK_OPENCODE_PROVIDERS, or move that model elsewhere in CRYSK_MODELS.
CRYSK-CONFIG-INVALID naming the models or credentials inputCRYSK_MODELS or CRYSK_CREDENTIALS is not valid JSON or breaks a rule (the step's log names the entry). Check the same object locally under models / credentials in ~/.crysk/config.json with npx -y crysk config, then set the variable again.
Blocking findings answered dismissed, gate still redgh pr comment <n> --body "/crysk recheck": the CI adjudicator rules on each dismissal (at most 5 per run). On upheld, comment /crysk review: that next review stops counting it. deferred / misclassified never clear the gate.
Gate error: CRYSK-GOTCHAS-MISSING ("the review instructions file (REVIEW.md or .crysk/gotchas.md) is empty or still the scaffold")Write real facts into that file and delete the human-attention-required marker line (or delete the file to review with the default guidance), commit it to the default branch, then comment /crysk review.
Gate error: CRYSK-HUNTERS-FAILED (every hunter failed)Check the route and credential first (the CRYSK-CRED-UNUSABLE and CRYSK-MODEL-UNAVAILABLE rows). Free OpenCode models fail intermittently: comment /crysk review to retry.
A /crysk review comment did nothingThe workflow is not on the default branch yet, the comment is not exact, the author lacks write access, or the workflow predates the comment trigger (re-scaffold with --force).

Review Settings Interview (ask the human, never choose for them)

Before step 4, ask the human these questions in their language. Use the native question UI when available (one grouped interaction is fine). Do not pick an answer for them, and do not skip a question because a default exists: the point is that they know these settings exist.

  1. Re-review level (how Crysk reviews new pushes on an open PR):
  • Minimal: one automatic review per PR; later pushes only on a /crysk review comment.
  • Balanced (recommended): re-review when the push touches risky files or the previous pass found enough (score >= 4); at most 2 automatic passes.
  • Thorough: review every push, up to 4 automatic passes. Most coverage, most cost.
  • Manual: nothing automatic after the first review; every re-review starts with /crysk review.
  1. Gate or advisory: gate turns the crysk check red on blocking findings (require it in branch protection to block merges); advisory keeps it green.
  2. How CI pays:
  • Claude subscription (CRYSK_CLAUDE_OAUTH_TOKEN): do not ask for a budget. Tell them no budget-usd is written: a subscription review spends quota, not dollars, and CI applies no ceiling while the run uses the subscription and no CRYSK_OPENCODE_* secret builds an OpenCode auth file (an OpenCode model brings back the $10 ceiling, so a subscription mixed with OpenCode is the API-key answer). An API key kept beside it is not used unless CRYSK_CREDENTIALS puts api_key first.
  • API key (CRYSK_CLAUDE_API_KEY or an OpenCode provider): ask for the spend ceiling per review in USD (default 10, 0 = none).
  1. Changed-lines threshold: a PR with more changed lines is skipped, not reviewed. Ask on any billing (default 4000, 0 = no limit, only if they say so): unlike the budget it matters on a subscription too, where an unset threshold means no limit at all.
  2. Advanced settings: name them, then ask whether to review them now. Each keeps a working default if skipped:
  • score weights: blocking 2, advisory 1 (integers >= 1; ci_blocking_weight, ci_advisory_weight), and the score floor 4 (ci_rereview_min_score); used only by the risk-aware and thresholded policies;
  • observe only (ci_admission_observe_only): log what the rules would skip, but review every push; good for one PR cycle;
  • trusted actors (ci_trusted_actors): extra GitHub logins whose Crysk markers count;
  • changed-files limit (max_changed_files): a PR touching more files is skipped; unset = none on a subscription, 50 on an API key;
  • exclusions: patterns in .cryskignore (gitignore syntax) the review never reads;
  • posting floor (post_min_severity): suggestion posts everything, warning (recommended, and what setup writes when the key is absent) hides advisory suggestions, blocking posts only blocking findings. Hidden findings are counted in the summary comment, and the gate is unchanged;
  • materiality gate (materiality_gate, off unless they say yes): blocking findings that are real but not material under normal use are posted as advisory instead of blocking, judged by an isolated sonnet call per blocking finding against Crysk's posting policy; security, credential and data-loss findings are never demoted. Tell them the cost (about one call per PR, +$0.015 notional, +10 s), that it runs on Claude only (claude:sonnet-latest, or claude:opus-latest through models.judge), so it needs a Claude secret, and the known limit: on a re-review, a finding that already blocked on an earlier push still counts toward the gate.

On a re-run (.crysk/config.json already has re-review keys, or the workflow already exists), first show the human the current values (npx -y crysk config) and offer Keep current settings for the level and for the line threshold. When they keep them, omit --level / --max-changed-lines: passing a flag overwrites that group, including a tuned max_verification_steps.

Then pass the answers to the scaffold as flags, never as hand-written YAML:

bash
npx -y crysk setup --ci --level <minimal|balanced|thorough|manual> --ci-mode <gate|advisory> --billing <subscription|api> --max-changed-lines <n> [--budget-usd <n>]

It writes the workflow, merges the level's keys into .crysk/config.json (keeping other keys), and prints a summary of every setting. Never run it without these flags: with none it applies balanced and gate, and its summary says nobody chose them. Write any advanced answers into .crysk/config.json (and .cryskignore) afterwards. The summary setup --ci printed predates those edits, so when there were any, show the human the effective settings from npx -y crysk config instead. Otherwise show the printed summary, including any Changed and Kept existing lines: on a re-run (for example --force to refresh an old workflow) only the groups a flag names are overwritten, and keys nobody chose stay as the file had them; the workflow keeps its old mode and budget-usd unless --ci-mode or --billing / --budget-usd is passed. In a terminal, every question defaults to the repository's current value. Details: references/ci-admission.md.

Execution Steps

  1. Inspect repo: git rev-parse --is-inside-work-tree, git remote get-url origin, gh auth status.
  2. Credential path: Claude-only → skip OpenCode. OpenCode or mix → read `references/opencode-ci.md` and execute it (models per role, one secret per provider, the providers variable).
  3. Claude secret (if used): gh secret set CRYSK_CLAUDE_OAUTH_TOKEN or CRYSK_CLAUDE_API_KEY (secure input, never print).
  4. Workflow: run the interview above, then npx -y crysk setup --ci with its flags. It writes .github/workflows/crysk.yml (or rewrites an existing pr-hero.yml in place) and the level keys in .crysk/config.json, and its next steps print the gh secret set / gh variable set commands for the person's ~/.crysk/config.json (models, credentials, OpenCode providers); run the ones the human agrees to. Confirm checks: write and actions: read, both pull_request and issue_comment triggers, the crysk-secrets: | block and the models / credentials lines. --force if an old template lacks them (an old credentials job, a missing issue_comment trigger, or claude-token / routing lines mean it predates the current workflow).
  5. Review instructions (optional, recommended before the first review): if the default branch has neither a root REVIEW.md nor .crysk/gotchas.md, run npx -y crysk init in the clone; it scaffolds REVIEW.md (an existing .crysk/gotchas.md is kept, and no REVIEW.md is written beside it). The agent writes the facts from the repository it has in context, not from the template: the deliberate oddity that looks like a bug, the invariant enforced outside the diff, the ownership rule a newcomer would break. The hunters and the refuter read the file as facts; the "Not blocking here" section is applied only by the materiality judge (materiality_gate: true, blocking findings only, and only to style, naming, test-hygiene, generated-code and dev-script findings), so fill it only when the human asked for that gate, and delete it otherwise. Delete the human-attention-required marker line (Crysk refuses to review while it is there), then commit the file to the default branch. With no file the review runs on the default guidance; an empty or scaffold file fails the run CRYSK-GOTCHAS-MISSING.
  6. Require the check: in branch protection, require the crysk status check (the gate), not the review job. The legacy pr-hero status is no longer posted, so a repository that still requires it is blocked until the rule moves to crysk. A private repository on GitHub Free cannot require status checks (HTTP 403): report that the gate is advisory there. With gh, and only after asking the human: read the current protection first (gh api repos/<o>/<r>/branches/<default>/protection), because the PUT replaces all of it; then gh api -X PUT repos/<o>/<r>/branches/<default>/protection with required_status_checks contexts ["crysk"].
  7. Advanced settings: write the answers from interview question 5 into .crysk/config.json (and .cryskignore), including post_min_severity when they chose a floor other than warning and materiality_gate: true only when they said yes; commit both to the default branch, and to any other branch PRs target (CI reads the config from the PR's base branch, so it applies from the next PR after the merge). No `models` or `credentials` key there (the repo parser refuses them). npx -y crysk config to verify.
  8. Verify: npx -y crysk doctor. git status. Confirm no echoed secret, and when OpenCode is on, that every opencode: model id in CRYSK_MODELS is one opencode models <provider> lists and each provider's token is in CRYSK_OPENCODE_PROVIDERS.
  9. Deploy: Offer commit. Open a same-repo test PR (forks skip).

Output Contract

Report:

  • Secret status (set or manual link). Names only: which CRYSK_* secrets exist (gh secret list). Never values.
  • Models (if set): the CRYSK_MODELS and CRYSK_CREDENTIALS JSON (no credentials in them), and for OpenCode the CRYSK_OPENCODE_PROVIDERS tokens and that each model id matches opencode models <provider>.
  • Workflow path (crysk.yml, or the pre-rename pr-hero.yml; both present means two reviews per PR, delete one) and whether checks: write, actions: read, the issue_comment trigger, the crysk-secrets block and the models / credentials lines are present, with no removed input left.
  • The review settings summary setup --ci printed (level, gate, budget, advanced settings), and which ones the human chose, including the posting floor (post_min_severity) and whether materiality_gate is on. Confirm repo .crysk/config.json has no models or credentials key.
  • npx -y crysk doctor / npx -y crysk config outcome.
  • Whether the default branch has a real REVIEW.md or .crysk/gotchas.md (no human-attention-required marker line), or neither (reviews run on the default guidance).
  • Whether crysk is a required check (or only the legacy pr-hero, which should move to crysk), or that the repository cannot require one (private repository on GitHub Free).
  • Next steps: merge the workflow to the default branch (the comment trigger needs it there), open a same-repo test PR, when to turn off observe-only. If CI skipped, the override is gh pr comment <n> --body "/crysk review".

References

  • assets/workflow.yml — the one review workflow (pull_request + issue_comment for /crysk review).
  • assets/admission-config.example.json — starter .crysk/config.json.
  • references/ci-admission.md — admission keys, modes, rollout, ledger.
  • references/opencode-ci.md — OpenCode secrets and variables, models per role, pin, openai vs deepseek.
  • docs/github-actions.md — full CI integration docs.
同じリポジトリから

関連する Skills

すべての Skills
cryskai
コミュニティ

crysk

Trigger: use or configure Crysk locally — change the review model or backend per role (models, fallback models, OpenCode, DeepSeek, custom model), effort, credentials order, config.json keys, REVIEW.md / gotchas.md, .cryskignore, size gate, run a review, crysk watch/gc, crysk doctor/config. Not CI (crysk-ci-setup) and not answering findings (crysk-loop).

1時間の導入数
2
GitHub Stars
14
更新日
11月12日
cryskai
コミュニティ

crysk-loop

Run the autonomous Crysk PR review loop end-to-end (review - judge - fix/reply - wait - recheck until done): triage Crysk findings posted as PR comments in their own thread with applied, dismissed, deferred, or misclassified plus reasoning, push verified fixes, and subscribe to re-reviews with crysk status --pr --wait --json without stopping to ask the user. Trigger: Crysk (formerly pr-hero) finding comments on a PR you authored, crysk-loop, pr-hero-loop, closing the PR review loop, responding t

1時間の導入数
2
GitHub Stars
14
更新日
11月12日
cryskai
コミュニティ

crysk-pr

Open or update a GitHub pull request with a structured title and reviewer-focused description, then automatically subscribe to the Crysk review via crysk status --pr --wait --json and hand off to crysk-loop if findings are reported. Trigger: open a PR, create a PR, gh pr create, submit PR, push branch and open PR, ship PR, crear PR, abrir PR.

1時間の導入数
2
GitHub Stars
14
更新日
11月12日