菜单
Filing and formatting GitHub issues: short bodies, repro steps, labels, multiline input. Use when creating or editing an issue.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Rust house style for repo-owned crates: edition 2024, naming, module layout, unsafe validation (Miri/loom/shuttle), mutation testing, fuzzing. Use when writing or reviewing Rust.
Use this skill to interactively debug Antithesis test runs using the multiverse debugger. Open a debugging-session URL, inspect container filesystems and runtime state, run shell commands, and extract evidence from inside the Antithesis environment. Supports both the simplified debugger (default) and the advanced notebook mode.
Search across all timelines in an Antithesis test run to find events, correlate property failures, and answer temporal questions about ordering and causation (e.g., did event A always precede failure B? do failures occur even without a preceding fault?).
Cross-cutting facts and gotchas for any Antithesis work on the ix repo — credentials, harness structure, `setup_complete` protocol, assertion idioms, randomness rules, workload design, triage via `agent-browser`, signed report URLs, and Test Composer script placement. Loads whenever an Antithesis run, report, property/assertion, `snouty` invocation, or `antithesis_sdk::` call is in play. Complements the task-scoped `antithesis-{setup,workload, launch,triage,debug,query-logs,research,documentation}` skills.
Triage Antithesis test reports to understand what happened in a run: look up runs, check status, investigate failed properties (assertions), view metadata, download logs, inspect findings, and examine environmental details. Load after a run completes or when investigating a failure.
Autonomously drive a pull request to merged by spawning a background subagent (the fork) that watches CI fail-fast, fixes each failure on the PR branch, re-pushes, and merges when green, all without blocking the main session. Use when the user wants to watch and merge a PR, babysit it, fix CI and merge, get a PR in, or otherwise hand off a PR's CI-to-merge loop so they can keep working. The skill never blocks the main thread; it launches the watcher and returns immediately.
| name | issues |
| description | Filing and formatting GitHub issues: short bodies, repro steps, labels, multiline input. Use when creating or editing an issue. |
Keep issue bodies short: problem, context, desired outcome. Bug reports need a concrete reproduction command or step list. Avoid prescribing implementation unless that is the actual request.
When creating or editing GitHub issue bodies or comments, pass multiline text
through a real multiline input path such as --body-file -, a temporary file, or
an editor. Escaped \n sequences in quoted --body strings render literally on
GitHub.
Prefer GitHub's suggestion block syntax for proposed inline changes in PR review
comments on changed lines. Use fenced suggestion blocks only when GitHub can
apply the snippet directly.
When work exposes a real bug, broken assumption, or unidiomatic pattern that will outlive the current task, file a GitHub issue right then. One concrete observation per issue.
Apply labels at filing time. Use labels to make the next action sortable:
bug, enhancement, documentation, rfc, help wanted, good first issue,
and ai-capable when an agent can plausibly finish the issue from the body
alone.
