ci-lint-test-gates
Define the evidence labels and tracked-location rules for local, deferred, and continuous-integration lint and test gates.
- License 许可
- MIT
- 所属仓库
- xiaden/SkyScow
- 最近更新
- 2026-09-30
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- ci-lint-test-gates
- description
- Define the evidence labels and tracked-location rules for local, deferred, and continuous-integration lint and test gates.
03 SKILL.md 正文
CI, Lint, and Test Gate Evidence
This global skill owns the evidence vocabulary for CI, lint, and test gates. It is global-only infrastructure: repository-specific skills may invoke these rules, but no repository mirror is required. Keep this canonical copy detailed and do not create a divergent same-name repository copy.
Evidence location
Commit required gate manifests and evidence to tracked repository paths. Never use the gitignored artifacts/ tree as the authoritative location. A static YAML file, manifest, or test configuration is not evidence that a gate ran.
Required labels
Preserve exactly one of these labels when reporting a gate:
LOCAL_PASS: the local lint or test command actually ran and passed.LOCAL_UNAVAILABLE: the local command could not run because its required tool, dependency, service, or environment was unavailable.CI_DEFERRED: execution is intentionally delegated to CI and no CI result is available yet.CI_PASS: tracked CI evidence proves that the configured gate ran and passed.
Integrity rules
- Do not relabel
LOCAL_UNAVAILABLEorCI_DEFERREDasCI_PASS. - Do not call an unwired test, an unexecuted command, or a manifest-only check
CI_PASS. - Preserve the producing gate's label through handoffs and summaries.
- Report the command, workflow, or evidence source that supports
LOCAL_PASSorCI_PASS. - If evidence is missing, retain
CI_DEFERREDor report the gate as unavailable; never silently infer success.
04 同仓库更多 Skills
unquoted-colon
暂无简介
quoted-description
Use when a plain scalar contains a colon: like this one.
block-description
Use when a plain scalar contains a colon: like this one.
work-routing
Canonical authority for who owns the next unit of work — direct work versus delegation, task tiers, bounded localization, the Change DAG size threshold, R&D evaluation routing, progressive research escalation, researcher scope signals, and QA/support owner selection. Use before choosing execution, investigation, design, or QA ownership; do not use to construct dispatch prompts, handoff schemas, or Change DAG/DD tool operation.
update-docs
Update project documentation to match code changes — generate codemaps, refresh READMEs, detect doc/code drift using AST analysis. Use when updating documentation after code changes, generating codemaps, verifying doc accuracy, or detecting stale documentation. Do NOT use for writing API reference docs from scratch (use doc-coauthoring) or for creating new skill files (use making-editing-skills).
skill-loading-system
Explain or troubleshoot OpenCode skill discovery, loading, permissions, availability, or prompt injection.