Review XQUIC harness structure for bloat, duplicated facts, trigger overlap, reference drift, and missing hard checks. Use when changing AGENTS.md, harness specs, pipelines, skills, setup scripts, validation routing, or when asked to audit harness design.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
This skill is a review gate for harness structure. It is usually read-only: produce findings first, then edit only when the user asks for fixes.
AGENTS.md, harness/README.md, and
harness/spec/harness-behavior.md.harness/docs/change-guide.md for the affected harness change type.bash harness/scripts/xqc_harness_check.sh after any committed-harness change.harness/spec/harness-manifest.yml.harness/spec/; informative documents do
not create independent requirements; rationale stays in
harness/decisions/..claude/ and .agents/ do not become required
committed sources.Use this order:
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Classify XQUIC GitHub issues with an evidence-backed L1-L4 resolution-complexity label while keeping validity, priority, severity, and disposition separate and skipping uniquely labeled issues unless the user explicitly forces a recheck. Use when triaging one issue or a batch of issues, creating an issue-complexity backlog, or applying or correcting L1-L4 GitHub labels.
日本語の概要は準備中です。原文の説明を表示しています。
Address actionable GitHub pull request review comments for xquic. Use when asked to handle PR review feedback, requested changes, unresolved inline threads, or reviewer comments while preserving unrelated edits.
日本語の概要は準備中です。原文の説明を表示しています。
Debug and fix failing GitHub PR checks for xquic. Use when a PR, branch, or commit has failed CI, GitHub Actions, build checks, test checks, or requested validation failures that should be diagnosed from logs before editing.
日本語の概要は準備中です。原文の説明を表示しています。
Verify whether a proposed XQUIC bug issue is real by checking the cited RFC or Internet-Draft mechanism against the repository's actual source behavior, tracing any root cause to current file and line evidence, and returning a fail-closed boolean gate. Use when validating an issue draft, investigating a claimed QUIC, HTTP/3, QPACK, or MoQT protocol violation, or before issue-submit may publish an issue.
日本語の概要は準備中です。原文の説明を表示しています。
Draft and submit evidence-backed XQUIC GitHub bug issues in the repository's CONTRIBUTING and issue-template format. Use when preparing or opening an alibaba/xquic issue that must identify an exact RFC or draft mechanism, expected-versus-actual behavior, reproduction evidence, and optional verified source root cause; requires issue-check to return true before any GitHub submission.
日本語の概要は準備中です。原文の説明を表示しています。
Enforce XQUIC test coverage and local validation gates. Use when code, build, or test changes need verification; before commit or pull request; or when asked to build, test, validate, or verify XQUIC. Requires paired happy-path and abnormal-path unit tests, the complete local unit suite, and explicit endpoint coverage or gap reporting for production behavior changes.
日本語の概要は準備中です。原文の説明を表示しています。