원클릭으로 Manus에서 모든 스킬 실행

ci-quality-gates

스타1

포크0

업데이트2026년 4월 29일 02:29

Use this skill when changing GitHub Actions, Makefile/package verification scripts, CI-required checks, build pipelines, or code that must pass local quality gates across ametel01 repos. It maps repo variants for Bun, Go, Scarb, frontend, indexer, and release workflows.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

ametel01

ametel01/orgs-ai-harness

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

CI Quality Gates

Purpose

Mirror each repo's CI locally and keep workflow, script, and documentation changes aligned.

When to use

Use when editing .github/workflows/**, Makefile, package.json scripts, Scarb.toml, build/test tooling, or when a code change needs final verification.

Evidence from repositories

Strength: Strong.

vitals-db: .github/workflows/ci.yml runs Bun install, check:ci, typecheck, test, build.
agents-toolbelt: .github/workflows/ci.yml runs make verify on Linux and macOS.
horizon-starknet: separate path-scoped workflows for Cairo build/fmt/lint/test, frontend CI, indexer CI, and release.
agents-toolbelt/CONTRIBUTING.md: documents make verify as canonical and says not to submit subsets only.

Standard workflow

Read the workflow that would run for the changed path.
Read the command source it invokes, such as package.json, Makefile, or Scarb.toml.
Run the closest local equivalent before reporting completion.
If changing the gate itself, update workflow files and docs together.
If a full gate is too expensive or blocked, run the narrowest matching subset and report the gap.

Commands

Area	CI-shaped checks
`vitals-db`	`bun install --frozen-lockfile`; `bun run check:ci`; `bun run typecheck`; `bun run test`; `bun run build`
`agents-toolbelt`	`make verify`
`horizon-starknet/contracts`	`scarb fmt --check`; `scarb check`; `scarb build`; `snforge test`
`horizon-starknet/packages/frontend`	`bun run typecheck`; `bun run lint`; `bun run format:check`; `bun test`; `bun run build`; e2e for UI flows
`horizon-starknet/packages/indexer`	`bun run typecheck`; `bun run lint`; `bun run format:check`; `bun run test`; `bun run build`

Required checks

Keep path filters aligned with the package or contract area they validate.
Use frozen installs in CI-like runs.
For CI edits, validate YAML syntax and command availability.
For gate changes, update contributor or README guidance if it names the old command.

Common pitfalls

Do not collapse horizon-starknet into one root CI command; its workflows are path-scoped.
Do not skip make verify in agents-toolbelt; it includes lint, race tests, build, and vulnerability checks.
Do not replace check:ci with check in vitals-db; CI uses warning-as-error behavior.

Escalation / uncertainty rules

If a workflow references a tool not installed locally, report the missing tool and run the remaining checks that do not depend on it. Do not mark the gate fully validated.

이 저장소의 다른 Skills

같은 저장소

harness-validation-tests

ametel01/orgs-ai-harness

Use this skill when adding or fixing orgs-ai-harness tests, validation rules, generated artifact schema checks, or local quality commands for the Python unittest suite.

2026-04-291

approval-eval-cache-lifecycle

ametel01/orgs-ai-harness

Use this skill when changing draft approval, protected artifact metadata, eval replay, verification thresholds, repo-local cache refresh, export policy, or explain output.

2026-04-291

github-repo-discovery

ametel01/orgs-ai-harness

Use this skill when modifying GitHub repository discovery, `gh repo list` integration, explicit repo selection, fork/archive filters, clone behavior, or interactive checkbox selection.

2026-04-291

harness-cli-workflows

ametel01/orgs-ai-harness

Use this skill when changing orgs-ai-harness CLI commands, setup wizard flows, argparse subcommands, user-facing command output, or command error handling in `src/orgs_ai_harness/cli.py`.

2026-04-291

harness-config-registry

ametel01/orgs-ai-harness

Use this skill when editing `harness.yml` parsing, repo registry mutations, org pack initialization, repo coverage statuses, or config round-trip behavior in orgs-ai-harness.

2026-04-291

harness-validation-tests

ametel01/orgs-ai-harness

Use this skill when adding or fixing orgs-ai-harness tests, validation rules, generated artifact schema checks, or local quality commands for the Python unittest suite.

2026-04-291

name	ci-quality-gates
description	Use this skill when changing GitHub Actions, Makefile/package verification scripts, CI-required checks, build pipelines, or code that must pass local quality gates across ametel01 repos. It maps repo variants for Bun, Go, Scarb, frontend, indexer, and release workflows.

CI Quality Gates

Purpose

Mirror each repo's CI locally and keep workflow, script, and documentation changes aligned.

When to use

Use when editing .github/workflows/**, Makefile, package.json scripts, Scarb.toml, build/test tooling, or when a code change needs final verification.

Evidence from repositories

Strength: Strong.

vitals-db: .github/workflows/ci.yml runs Bun install, check:ci, typecheck, test, build.
agents-toolbelt: .github/workflows/ci.yml runs make verify on Linux and macOS.
horizon-starknet: separate path-scoped workflows for Cairo build/fmt/lint/test, frontend CI, indexer CI, and release.
agents-toolbelt/CONTRIBUTING.md: documents make verify as canonical and says not to submit subsets only.

Standard workflow

Read the workflow that would run for the changed path.
Read the command source it invokes, such as package.json, Makefile, or Scarb.toml.
Run the closest local equivalent before reporting completion.
If changing the gate itself, update workflow files and docs together.
If a full gate is too expensive or blocked, run the narrowest matching subset and report the gap.

Commands

Area	CI-shaped checks
`vitals-db`	`bun install --frozen-lockfile`; `bun run check:ci`; `bun run typecheck`; `bun run test`; `bun run build`
`agents-toolbelt`	`make verify`
`horizon-starknet/contracts`	`scarb fmt --check`; `scarb check`; `scarb build`; `snforge test`
`horizon-starknet/packages/frontend`	`bun run typecheck`; `bun run lint`; `bun run format:check`; `bun test`; `bun run build`; e2e for UI flows
`horizon-starknet/packages/indexer`	`bun run typecheck`; `bun run lint`; `bun run format:check`; `bun run test`; `bun run build`

Required checks

Keep path filters aligned with the package or contract area they validate.
Use frozen installs in CI-like runs.
For CI edits, validate YAML syntax and command availability.
For gate changes, update contributor or README guidance if it names the old command.

Common pitfalls

Do not collapse horizon-starknet into one root CI command; its workflows are path-scoped.
Do not skip make verify in agents-toolbelt; it includes lint, race tests, build, and vulnerability checks.
Do not replace check:ci with check in vitals-db; CI uses warning-as-error behavior.

Escalation / uncertainty rules

If a workflow references a tool not installed locally, report the missing tool and run the remaining checks that do not depend on it. Do not mark the gate fully validated.