[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M753N1EGF2GAHDYEDBKJEFGS":3,"skill-same:01M753N1EGF2GAHDYEDBKJEFGS":47},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":30,"ownerHtmlUrl":31,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":32,"install":33,"resources":46},"01M753N1EGF2GAHDYEDBKJEFGS","apex-ray",null,"Use when running or configuring Apex Ray local code reviews, interpreting reports, continuing partial reviews, tuning rules, memory, telemetry, or historical PR evals.","dobrotacreator\u002Fapex-ray","dobrotacreator","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F45421346?v=4","01M753MV20YAW2806STN5Q9J16","Igor Pavlyukovets","01M753MV2XEMKV2HQ1CS8972BH",7,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fdobrotacreator\u002Fapex-ray\u002Fblob\u002Fmain\u002F.apex-ray\u002Fskills\u002Fapex-ray\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: apex-ray\ndescription: Use when running or configuring Apex Ray local code reviews, interpreting reports, continuing partial reviews, tuning rules, memory, telemetry, or historical PR evals.\napex_ray_template_version: 5\n---\n\n# Apex Ray\n\n## Purpose\n\nApex Ray is the project's local diff-aware AI review tool. Use it to create deterministic local review reports, run configured LLM review, continue partial coverage, tune repo rules\u002Fmemory, inspect telemetry, and replay historical PR evals.\n\n## Process\n\n- Run `uv run --locked apex-ray doctor` when setup, config, provider, or analyzer state is uncertain.\n- When Apex Ray is configured in a pre-push hook, do not proactively run `uv run --locked apex-ray review` or `uv run --locked apex-ray gate pre-push` as a routine final verification step; let `git push` invoke the hook so the pre-push incremental retry state remains the source of truth.\n- For deterministic local review outside pre-push, run `uv run --locked apex-ray review --no-llm` only when the user asks or when diagnosing Apex Ray; default reports are written under `.apex-ray\u002Freports\u002F`.\n- When the user asks, the hook is unavailable, or explicit pre-push gate parity is needed before pushing, run `uv run --locked apex-ray gate pre-push`; blocking findings and critical partial coverage are printed to stdout and the full report is written under `.apex-ray\u002Freports\u002F`.\n- Do not bypass the configured pre-push gate by default. Use `uv run --locked apex-ray findings suppress` only for confirmed local false positives after checking the finding evidence, current code, and relevant tests or invariants. Provide a concrete objective reason; do not suppress uncertain findings, real defects, or findings merely to get a push through.\n- If bypassing is unavoidable, explain why and name the equivalent checks or review already run.\n- Use `--no-llm` or `.apex-ray\u002Fconfig.local.yml` when the configured local provider is unavailable or LLM cost is not appropriate.\n- Use `.apex-ray\u002Fconfig.yml` for shared team policy and `.apex-ray\u002Fconfig.local.yml` for personal provider\u002Fmodel\u002Fcost overrides.\n- Use `.apex-ray\u002Frules\u002F` for stable review rules and `.apex-ray\u002Fmemory\u002F` for curated team learning.\n- Use `uv run --locked apex-ray telemetry-summary` when tuning cost, latency, coverage, or model routing.\n- Treat `.apex-ray\u002Freports\u002F*.md\u002Fjson\u002Fhtml` as latest snapshots. Archived run reports live under configured local data when `review.reports.archive: true`.\n- Treat `.apex-ray\u002Ftriage\u002F` as local ephemeral finding state and audit events; do not commit raw suppressions.\n- Use `uv run --locked apex-ray eval capture-prs` and `uv run --locked apex-ray eval run-prs` only for historical PR benchmark\u002Feval work.\n\n### Coverage And Continuation\n\n- Findings apply only to the reviewed scope. Before describing a diff as clean, inspect `llm_coverage.completion_status`, unique context-pack coverage, reviewer-assignment coverage, and `llm_coverage.coverage_todos`. For `partial` or `incomplete`, state the material remaining debt; zero findings does not mean the whole diff was reviewed cleanly.\n- Read the full JSON `coverage_todos`: each item identifies the pack, reason, `suggested_command`, and reviewer when applicable. Prefer that targeted command, or deliberately select unreviewed debt with `uv run --locked apex-ray review --continue-from .apex-ray\u002Freports\u002Freview.json --residual-priority p0 --llm`, repeatable `--only-pack`, or `--only-slice`. An ordinary continuation is one budgeted pass and may need to be repeated.\n- Continue when the user asks, the gate or team policy requires it, or material uncovered risk remains. Prefer P0, high-risk, and exact-pack work, respect configured budgets, and do not raise caps or drain optional reviewer scopes solely to turn the status green.\n- When one baseline reviewer scope must finish, run `uv run --locked apex-ray review --continue-from .apex-ray\u002Freports\u002Freview.json --reviewer '\u003Cbaseline-reviewer-id>' --until-complete --strict-coverage --llm --json .apex-ray\u002Freports\u002Freview.json`. `--strict-coverage` exits non-zero if bounded completion cannot finish. Completion covers only the selected reviewer's matching assignments; a completed specialist scope does not imply global completion. Use an unfiltered baseline reviewer when the whole reviewable diff must be covered, then re-check report-level coverage.\n- Continuation validates the saved review target. If Apex Ray rejects a stale or changed target, run a fresh review instead of reusing archived packs.\n\n## Outputs\n\nPrefer writing generated review artifacts under `.apex-ray\u002Freports\u002F`. Keep Markdown, JSON, and HTML reports together when possible so humans and automation can inspect the same run.\n\n## Boundaries\n\nDo not treat Apex Ray as a replacement for tests, linters, typecheck, CI, dependency scanners, SAST, or human review. Do not commit `.apex-ray\u002Fconfig.local.yml`, `.apex-ray\u002Fcache\u002F`, `.apex-ray\u002Ftelemetry\u002F`, `.apex-ray\u002Freports\u002F`, eval run directories, generated review artifacts, or local provider, model, API, or cost settings unless the team intentionally curates a specific artifact.\n\n### Local Finding Triage\n\nWhen a pre-push finding is a confirmed local false positive, suppress the specific finding locally instead of bypassing the hook:\n\n```bash\nuv run --locked apex-ray findings list --from-report .apex-ray\u002Freports\u002Fpre-push.json\nuv run --locked apex-ray findings suppress apex-ID \\\n  --from-report .apex-ray\u002Freports\u002Fpre-push.json \\\n  --reason \"The repository layer already enforces this invariant.\"\n```\n\nUse suppressions sparingly. Before suppressing, inspect the finding evidence, the current code, and relevant tests, invariants, or ownership assumptions. The reason must be concrete and objective enough for a later agent to audit. Do not suppress when the finding might be real, when you are unsure, or merely to get a push through.\n\nTriage state is local and ignored by default. It is intended for frequent local review runs, not as shared team policy. A suppression applies only while the finding fingerprint and context-pack fingerprint still match; if relevant context changes, Apex Ray marks the suppression stale, prints the prior reason, and lets the finding block again. Re-check stale findings before suppressing again.\n\nUseful cleanup commands:\n\n```bash\nuv run --locked apex-ray findings suppressions\nuv run --locked apex-ray findings unsuppress sup-ID\nuv run --locked apex-ray findings prune\n```\n","# Apex Ray\n\n## Purpose\n\nApex Ray is the project's local diff-aware AI review tool. Use it to create deterministic local review reports, run configured LLM review, continue partial coverage, tune repo rules\u002Fmemory, inspect telemetry, and replay historical PR evals.\n\n## Process\n\n- Run `uv run --locked apex-ray doctor` when setup, config, provider, or analyzer state is uncertain.\n- When Apex Ray is configured in a pre-push hook, do not proactively run `uv run --locked apex-ray review` or `uv run --locked apex-ray gate pre-push` as a routine final verification step; let `git push` invoke the hook so the pre-push incremental retry state remains the source of truth.\n- For deterministic local review outside pre-push, run `uv run --locked apex-ray review --no-llm` only when the user asks or when diagnosing Apex Ray; default reports are written under `.apex-ray\u002Freports\u002F`.\n- When the user asks, the hook is unavailable, or explicit pre-push gate parity is needed before pushing, run `uv run --locked apex-ray gate pre-push`; blocking findings and critical partial coverage are printed to stdout and the full report is written under `.apex-ray\u002Freports\u002F`.\n- Do not bypass the configured pre-push gate by default. Use `uv run --locked apex-ray findings suppress` only for confirmed local false positives after checking the finding evidence, current code, and relevant tests or invariants. Provide a concrete objective reason; do not suppress uncertain findings, real defects, or findings merely to get a push through.\n- If bypassing is unavoidable, explain why and name the equivalent checks or review already run.\n- Use `--no-llm` or `.apex-ray\u002Fconfig.local.yml` when the configured local provider is unavailable or LLM cost is not appropriate.\n- Use `.apex-ray\u002Fconfig.yml` for shared team policy and `.apex-ray\u002Fconfig.local.yml` for personal provider\u002Fmodel\u002Fcost overrides.\n- Use `.apex-ray\u002Frules\u002F` for stable review rules and `.apex-ray\u002Fmemory\u002F` for curated team learning.\n- Use `uv run --locked apex-ray telemetry-summary` when tuning cost, latency, coverage, or model routing.\n- Treat `.apex-ray\u002Freports\u002F*.md\u002Fjson\u002Fhtml` as latest snapshots. Archived run reports live under configured local data when `review.reports.archive: true`.\n- Treat `.apex-ray\u002Ftriage\u002F` as local ephemeral finding state and audit events; do not commit raw suppressions.\n- Use `uv run --locked apex-ray eval capture-prs` and `uv run --locked apex-ray eval run-prs` only for historical PR benchmark\u002Feval work.\n\n### Coverage And Continuation\n\n- Findings apply only to the reviewed scope. Before describing a diff as clean, inspect `llm_coverage.completion_status`, unique context-pack coverage, reviewer-assignment coverage, and `llm_coverage.coverage_todos`. For `partial` or `incomplete`, state the material remaining debt; zero findings does not mean the whole diff was reviewed cleanly.\n- Read the full JSON `coverage_todos`: each item identifies the pack, reason, `suggested_command`, and reviewer when applicable. Prefer that targeted command, or deliberately select unreviewed debt with `uv run --locked apex-ray review --continue-from .apex-ray\u002Freports\u002Freview.json --residual-priority p0 --llm`, repeatable `--only-pack`, or `--only-slice`. An ordinary continuation is one budgeted pass and may need to be repeated.\n- Continue when the user asks, the gate or team policy requires it, or material uncovered risk remains. Prefer P0, high-risk, and exact-pack work, respect configured budgets, and do not raise caps or drain optional reviewer scopes solely to turn the status green.\n- When one baseline reviewer scope must finish, run `uv run --locked apex-ray review --continue-from .apex-ray\u002Freports\u002Freview.json --reviewer '\u003Cbaseline-reviewer-id>' --until-complete --strict-coverage --llm --json .apex-ray\u002Freports\u002Freview.json`. `--strict-coverage` exits non-zero if bounded completion cannot finish. Completion covers only the selected reviewer's matching assignments; a completed specialist scope does not imply global completion. Use an unfiltered baseline reviewer when the whole reviewable diff must be covered, then re-check report-level coverage.\n- Continuation validates the saved review target. If Apex Ray rejects a stale or changed target, run a fresh review instead of reusing archived packs.\n\n## Outputs\n\nPrefer writing generated review artifacts under `.apex-ray\u002Freports\u002F`. Keep Markdown, JSON, and HTML reports together when possible so humans and automation can inspect the same run.\n\n## Boundaries\n\nDo not treat Apex Ray as a replacement for tests, linters, typecheck, CI, dependency scanners, SAST, or human review. Do not commit `.apex-ray\u002Fconfig.local.yml`, `.apex-ray\u002Fcache\u002F`, `.apex-ray\u002Ftelemetry\u002F`, `.apex-ray\u002Freports\u002F`, eval run directories, generated review artifacts, or local provider, model, API, or cost settings unless the team intentionally curates a specific artifact.\n\n### Local Finding Triage\n\nWhen a pre-push finding is a confirmed local false positive, suppress the specific finding locally instead of bypassing the hook:\n\n```bash\nuv run --locked apex-ray findings list --from-report .apex-ray\u002Freports\u002Fpre-push.json\nuv run --locked apex-ray findings suppress apex-ID \\\n  --from-report .apex-ray\u002Freports\u002Fpre-push.json \\\n  --reason \"The repository layer already enforces this invariant.\"\n```\n\nUse suppressions sparingly. Before suppressing, inspect the finding evidence, the current code, and relevant tests, invariants, or ownership assumptions. The reason must be concrete and objective enough for a later agent to audit. Do not suppress when the finding might be real, when you are unsure, or merely to get a push through.\n\nTriage state is local and ignored by default. It is intended for frequent local review runs, not as shared team policy. A suppression applies only while the finding fingerprint and context-pack fingerprint still match; if relevant context changes, Apex Ray marks the suppression stale, prints the prior reason, and lets the finding block again. Re-check stale findings before suppressing again.\n\nUseful cleanup commands:\n\n```bash\nuv run --locked apex-ray findings suppressions\nuv run --locked apex-ray findings unsuppress sup-ID\nuv run --locked apex-ray findings prune\n```\n",{"name":5,"description":7,"apex_ray_template_version":24},5,"main","afd558ef175b19cbcfca6412244e7d96c762482a",".apex-ray\u002Fskills\u002Fapex-ray",0,"https:\u002F\u002Fgithub.com\u002Fdobrotacreator\u002Fapex-ray","https:\u002F\u002Fdobrotacreator.github.io\u002Fapex-ray\u002F","https:\u002F\u002Fgithub.com\u002Fdobrotacreator","2026-11-05 08:24:11",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add dobrotacreator\u002Fapex-ray --skill apex-ray",{"tool":39,"command":40},"bunx","bunx skills add dobrotacreator\u002Fapex-ray --skill apex-ray",{"tool":42,"command":43},"pnpm","pnpm dlx skills add dobrotacreator\u002Fapex-ray --skill apex-ray","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdobrotacreator\u002Fapex-ray\u002Fblob\u002Fmain\u002F.apex-ray\u002Fskills\u002Fapex-ray\u002FSKILL.md",true,[],[48,53,59],{"skillNo":49,"name":5,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":19},"01M753N649C2RZ85Q0DBE42B51","https:\u002F\u002Fgithub.com\u002Fdobrotacreator\u002Fapex-ray\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fapex-ray\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":19},"01M753N4SRX1Z1E3S9KCH5WFER","apex-ray-improve","https:\u002F\u002Fgithub.com\u002Fdobrotacreator\u002Fapex-ray\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fapex-ray-improve\u002FSKILL.md",[],[],{"skillNo":60,"name":55,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":19},"01M753MXGR23GSNCXWHBQQ2PNW","Use after merged PRs or review feedback to produce recommendation-only improvements for Apex Ray memory, rules, eval labels, telemetry, coverage, model routing, or config from PR comments, Greptile findings, Apex reports, and telemetry.","https:\u002F\u002Fgithub.com\u002Fdobrotacreator\u002Fapex-ray\u002Fblob\u002Fmain\u002F.apex-ray\u002Fskills\u002Fapex-ray-improve\u002FSKILL.md",[],[]]