본문으로 건너뛰기
cccskills
무료GitHub에 공개

harness-review

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

alibaba/xquic
설치 방법 보기

포함된 파일(1)

  • SKILL.md2.0 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

Harness Review

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.

Review Inputs

  1. Read AGENTS.md, harness/README.md, and harness/spec/harness-behavior.md.
  2. Read harness/docs/change-guide.md for the affected harness change type.
  3. Read the changed specs, pipelines, skills, setup scripts, or validation scripts.
  4. Run bash harness/scripts/xqc_harness_check.sh after any committed-harness change.

Checks

  • Strong injection stays small and points to durable sources instead of repeating them.
  • New procedures live in skills or pipelines, not root instructions.
  • Machine mappings stay in harness/spec/harness-manifest.yml.
  • Normative requirements stay in harness/spec/; informative documents do not create independent requirements; rationale stays in harness/decisions/.
  • Document authority is independent of whether a human or agent consumes it.
  • Skill descriptions declare a narrow trigger. Skill bodies declare ownership boundaries and avoid competing with existing skills.
  • Repeated requirements have one source of truth; other files link to it.
  • "Always" or "never" requirements that must be reliable have a script, hook, schema check, or permission guard where practical.
  • Local adapters such as .claude/ and .agents/ do not become required committed sources.

Output

Use this order:

  1. Findings: bloat, duplicate facts, overlapping triggers, broken references, missing hard checks.
  2. Decisions needed: only items that require user policy choice.
  3. Proposed movement: keep, merge, delete, move to manifest, move to spec, move to skill, or move to script/hook.
  4. Validation: exact harness checks run or still needed.

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

classify-issue-complexity

무료

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

alibaba/xquic1.9천2026년 10월 22일 업데이트

gh-address-comments

무료

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

alibaba/xquic1.9천2026년 10월 22일 업데이트

gh-fix-ci

무료

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

alibaba/xquic1.9천2026년 10월 22일 업데이트

issue-check

무료

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

alibaba/xquic1.9천2026년 10월 22일 업데이트

issue-submit

무료

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

alibaba/xquic1.9천2026년 10월 22일 업데이트

validate

무료

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

alibaba/xquic1.9천2026년 10월 22일 업데이트

alibaba의 스킬 모두 보기

이 스킬의 문제 신고