vibe-ci-supply-chain
Git workflow, CI/GitHub Actions, and supply-chain pinning rules for Mistral Vibe. Use when changing CI pipelines, GitHub Actions, dependency pinning, container images, pre-commit hooks, git workflow, or external binary downloads.
- License 许可
- Apache-2.0
- 最近更新
- 2026-08-23
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- vibe-ci-supply-chain
- metadata
- { "display-name": "Vibe CI & Supply Chain", "default-prompt": "Use $vibe-ci-supply-chain to follow Vibe git, CI, and supply-chain conventions.", "short-description": "Git, CI, and supply-chain pinning for Vibe" }
- description
- Git workflow, CI/GitHub Actions, and supply-chain pinning rules for Mistral Vibe. Use when changing CI pipelines, GitHub Actions, dependency pinning, container images, pre-commit hooks, git workflow, or external binary downloads.
03 SKILL.md 正文
Vibe CI & Supply Chain
Conventions for git workflow, CI configuration, and supply-chain security in Vibe.
Startup import cost
CI gates cold-start module count via vibe/scripts/check_startup_import_cost.py (budgets in vibe/scripts/startup_import_cost.vibe.toml).
- When a change touches imports or module structure on the path of
import vibeorfrom vibe.cli.textual_ui.app import VibeApp, runcd vibe && uv run scripts/check_startup_import_cost.pyand confirm the count stays within budget. - Verify, do not bump. An overshoot is a regression to investigate (lazy import, drop the dependency, defer the import) — not a reason to raise the budget. Only widen for a deliberate, PR-justified increase, and set to observed count + ~10% headroom, never the exact count.
Git
- Never use
git commit --amend,git push --force, orgit push --force-with-lease. - Always create new commits and push with a plain
git push. - Reconciling with the upstream of the current branch (e.g. push rejected because
origin/<current-branch>advanced): rebase the current branch onto its upstream — do not merge the upstream branch into the current one, never force-push. - Reconciling with the base branch (e.g.
origin/main) once the PR is open: merge the base branch into the current branch — do not rebase, since rebasing rewrites already-pushed history and would require a force-push. - Run git commands through
uv run(e.g.uv run git commit,uv run git push) so pre-commit hooks resolve the project's venv — baregit commitfails pre-commit withreportMissingImportsbecause pyright can't find third-party packages.
CI / GitHub Actions
- Pin every
uses:to a full commit SHA with an exact version comment:uses: owner/action@<commit-sha> # vX.Y.Z. - Resolve to the commit, not the annotated-tag object: take the
refs/tags/vX^{}line fromgit ls-remote --tags, orgh api repos/<owner>/<repo>/git/refs/tags/<tag> --jq .objectpeeled to a commit. Check withgit cat-file -t <sha>→commit, nottag. Never pin a moving major tag (v9).
Supply-chain pinning
Every external input to the build, CI, or install path must be pinned to an immutable identifier — never a mutable tag or an unverified download. Add a human-readable comment next to each pin.
- Container images: reference by
@sha256:<digest>, never a bare tag (:latest,:8). Resolve the digest via the registry'sDocker-Content-Digestheader (curl -sI -H 'Accept: application/vnd.oci.image.index.v1+json' <registry>/v2/<repo>/manifests/<tag>). When the image lives inside a JSON matrix string, document the tag→digest mapping in an adjacent comment. - pre-commit hooks (
.pre-commit-config.yaml): pin everyrev:to a full commit SHA with a# vX.Y.Zcomment. Runpre-commit autoupdate --freezeto refresh, and resolve to the peeled commit ref (refs/tags/vX^{}), not the annotated-tag object — same rule asuses:above. - Build-system deps (
pyproject.toml[build-system] requires): pinhatchling,hatch-vcs,editables(and any addition) to exact==versions. These execute during source builds and are not covered byuv.lock. - External binary downloads (e.g.
patchelfinscripts/ci/): never pipe an unverified download straight intotar/sh. Download to a temp file, verifysha256sum -cagainst a known-good hash keyed by version (and arch when relevant), then extract. Hard-fail when no hash is registered for the requested version/arch so a bump forces updating the hash.
04 同仓库更多 Skills
prompts
暂无简介
write-vibe-tests
Write or refactor Mistral Vibe tests with proper decoupling. Use when adding behavior coverage, testing ports/adapters, replacing brittle mocks, creating fakes, adding characterization tests before refactors, or changing tests under tests/ for vibe/core, vibe/cli, vibe/acp, tools, config, sessions, skills, hooks, MCP, or setup.
write-vibe-adr
Create or update Architecture Decision Records for the Mistral Vibe Python CLI. Use when a design discussion creates a new architectural constraint, when an undocumented convention causes confusion or review feedback, or when architecture guidance in docs/adr or AGENTS.md must be changed.
instrument-feature-analytics
Plan analytics instrumentation for a feature. Use when implementing any feature — every feature must ship with telemetry. Decides which events and properties the metrics need (funnels, adoption, status flows), checks compatibility with the existing datalake and event registry, and walks through local, staging, and production verification.
create-vibe-feature
Add or modify a feature in the Mistral Vibe Python CLI while following the app architecture ADRs. Use when working in vibe/core, vibe/cli, vibe/acp, vibe/setup, built-in tools, config, sessions, skills, hooks, MCP, connectors, or other Vibe feature code.
vibe-textual-ui
Textual TUI widget and TCSS conventions for Mistral Vibe. Use when building or styling Textual widgets, writing TCSS rules, working with selectable lists, tool headers, theme variables, or UI component layout.