[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AZQJH0CTEKM7ZXADK8VBAH":3,"skill-same:01M7AZQJH0CTEKM7ZXADK8VBAH":49},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":28,"commitSha":29,"skillDirectory":30,"forksCount":14,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":6,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M7AZQJH0CTEKM7ZXADK8VBAH","vibe-ci-supply-chain",null,"Git workflow, CI\u002FGitHub 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.","Mr-Shine09\u002FZephyr","Mr-Shine09","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F203695007?v=4","01M7AZPSSR44CHX8AQ7WKA37B9","Oak Soe Khant","01M7AZPSTCHZF7XBHVFSNSP7CB",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FMr-Shine09\u002FZephyr\u002Fblob\u002Fcompanion\u002F.agents\u002Fskills\u002Fvibe-ci-supply-chain\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: vibe-ci-supply-chain\ndescription: Git workflow, CI\u002FGitHub 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.\nmetadata:\n  display-name: Vibe CI & Supply Chain\n  short-description: Git, CI, and supply-chain pinning for Vibe\n  default-prompt: Use $vibe-ci-supply-chain to follow Vibe git, CI, and supply-chain conventions.\n---\n\n# Vibe CI & Supply Chain\n\nConventions for git workflow, CI configuration, and supply-chain security in Vibe.\n\n## Startup import cost\n\nCI gates cold-start module count via `vibe\u002Fscripts\u002Fcheck_startup_import_cost.py` (budgets in `vibe\u002Fscripts\u002Fstartup_import_cost.vibe.toml`).\n\n- When a change touches imports or module structure on the path of `import vibe` or `from vibe.cli.textual_ui.app import VibeApp`, run `cd vibe && uv run scripts\u002Fcheck_startup_import_cost.py` and confirm the count stays within budget.\n- **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.\n\n## Git\n\n- Never use `git commit --amend`, `git push --force`, or `git push --force-with-lease`.\n- Always create new commits and push with a plain `git push`.\n- Reconciling with the upstream of the current branch (e.g. push rejected because `origin\u002F\u003Ccurrent-branch>` advanced): rebase the current branch onto its upstream — do not merge the upstream branch into the current one, never force-push.\n- Reconciling with the base branch (e.g. `origin\u002Fmain`) 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.\n- 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 — bare `git commit` fails pre-commit with `reportMissingImports` because pyright can't find third-party packages.\n\n## CI \u002F GitHub Actions\n\n- Pin every `uses:` to a full **commit SHA** with an exact version comment: `uses: owner\u002Faction@\u003Ccommit-sha> # vX.Y.Z`.\n- Resolve to the commit, not the annotated-tag object: take the `refs\u002Ftags\u002FvX^{}` line from `git ls-remote --tags`, or `gh api repos\u002F\u003Cowner>\u002F\u003Crepo>\u002Fgit\u002Frefs\u002Ftags\u002F\u003Ctag> --jq .object` peeled to a commit. Check with `git cat-file -t \u003Csha>` → `commit`, not `tag`. Never pin a moving major tag (`v9`).\n\n## Supply-chain pinning\n\nEvery 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.\n\n- **Container images**: reference by `@sha256:\u003Cdigest>`, never a bare tag (`:latest`, `:8`). Resolve the digest via the registry's `Docker-Content-Digest` header (`curl -sI -H 'Accept: application\u002Fvnd.oci.image.index.v1+json' \u003Cregistry>\u002Fv2\u002F\u003Crepo>\u002Fmanifests\u002F\u003Ctag>`). When the image lives inside a JSON matrix string, document the tag→digest mapping in an adjacent comment.\n- **pre-commit hooks** (`.pre-commit-config.yaml`): pin every `rev:` to a full commit SHA with a `# vX.Y.Z` comment. Run `pre-commit autoupdate --freeze` to refresh, and resolve to the peeled commit ref (`refs\u002Ftags\u002FvX^{}`), not the annotated-tag object — same rule as `uses:` above.\n- **Build-system deps** (`pyproject.toml` `[build-system] requires`): pin `hatchling`, `hatch-vcs`, `editables` (and any addition) to exact `==` versions. These execute during source builds and are not covered by `uv.lock`.\n- **External binary downloads** (e.g. `patchelf` in `scripts\u002Fci\u002F`): never pipe an unverified download straight into `tar`\u002F`sh`. Download to a temp file, verify `sha256sum -c` against a known-good hash keyed by version (and arch when relevant), then extract. Hard-fail when no hash is registered for the requested version\u002Farch so a bump forces updating the hash.\n","# Vibe CI & Supply Chain\n\nConventions for git workflow, CI configuration, and supply-chain security in Vibe.\n\n## Startup import cost\n\nCI gates cold-start module count via `vibe\u002Fscripts\u002Fcheck_startup_import_cost.py` (budgets in `vibe\u002Fscripts\u002Fstartup_import_cost.vibe.toml`).\n\n- When a change touches imports or module structure on the path of `import vibe` or `from vibe.cli.textual_ui.app import VibeApp`, run `cd vibe && uv run scripts\u002Fcheck_startup_import_cost.py` and confirm the count stays within budget.\n- **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.\n\n## Git\n\n- Never use `git commit --amend`, `git push --force`, or `git push --force-with-lease`.\n- Always create new commits and push with a plain `git push`.\n- Reconciling with the upstream of the current branch (e.g. push rejected because `origin\u002F\u003Ccurrent-branch>` advanced): rebase the current branch onto its upstream — do not merge the upstream branch into the current one, never force-push.\n- Reconciling with the base branch (e.g. `origin\u002Fmain`) 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.\n- 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 — bare `git commit` fails pre-commit with `reportMissingImports` because pyright can't find third-party packages.\n\n## CI \u002F GitHub Actions\n\n- Pin every `uses:` to a full **commit SHA** with an exact version comment: `uses: owner\u002Faction@\u003Ccommit-sha> # vX.Y.Z`.\n- Resolve to the commit, not the annotated-tag object: take the `refs\u002Ftags\u002FvX^{}` line from `git ls-remote --tags`, or `gh api repos\u002F\u003Cowner>\u002F\u003Crepo>\u002Fgit\u002Frefs\u002Ftags\u002F\u003Ctag> --jq .object` peeled to a commit. Check with `git cat-file -t \u003Csha>` → `commit`, not `tag`. Never pin a moving major tag (`v9`).\n\n## Supply-chain pinning\n\nEvery 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.\n\n- **Container images**: reference by `@sha256:\u003Cdigest>`, never a bare tag (`:latest`, `:8`). Resolve the digest via the registry's `Docker-Content-Digest` header (`curl -sI -H 'Accept: application\u002Fvnd.oci.image.index.v1+json' \u003Cregistry>\u002Fv2\u002F\u003Crepo>\u002Fmanifests\u002F\u003Ctag>`). When the image lives inside a JSON matrix string, document the tag→digest mapping in an adjacent comment.\n- **pre-commit hooks** (`.pre-commit-config.yaml`): pin every `rev:` to a full commit SHA with a `# vX.Y.Z` comment. Run `pre-commit autoupdate --freeze` to refresh, and resolve to the peeled commit ref (`refs\u002Ftags\u002FvX^{}`), not the annotated-tag object — same rule as `uses:` above.\n- **Build-system deps** (`pyproject.toml` `[build-system] requires`): pin `hatchling`, `hatch-vcs`, `editables` (and any addition) to exact `==` versions. These execute during source builds and are not covered by `uv.lock`.\n- **External binary downloads** (e.g. `patchelf` in `scripts\u002Fci\u002F`): never pipe an unverified download straight into `tar`\u002F`sh`. Download to a temp file, verify `sha256sum -c` against a known-good hash keyed by version (and arch when relevant), then extract. Hard-fail when no hash is registered for the requested version\u002Farch so a bump forces updating the hash.\n",{"name":5,"metadata":24,"description":7},{"display-name":25,"default-prompt":26,"short-description":27},"Vibe CI & Supply Chain","Use $vibe-ci-supply-chain to follow Vibe git, CI, and supply-chain conventions.","Git, CI, and supply-chain pinning for Vibe","companion","de27bf496077835506f1e45c5210c2b3aef5622f",".agents\u002Fskills\u002Fvibe-ci-supply-chain","https:\u002F\u002Fgithub.com\u002FMr-Shine09\u002FZephyr","https:\u002F\u002Fgithub.com\u002FMr-Shine09","Computer Engineering Student @ De Anza College | Embedded Systems, IoT & Software | Built an Infineon-Sponsored Assistive Device | Open to Internships","2026-08-23 08:52:57",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add Mr-Shine09\u002FZephyr --skill vibe-ci-supply-chain",{"tool":41,"command":42},"bunx","bunx skills add Mr-Shine09\u002FZephyr --skill vibe-ci-supply-chain",{"tool":44,"command":45},"pnpm","pnpm dlx skills add Mr-Shine09\u002FZephyr --skill vibe-ci-supply-chain","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMr-Shine09\u002FZephyr\u002Fblob\u002Fcompanion\u002F.agents\u002Fskills\u002Fvibe-ci-supply-chain\u002FSKILL.md",true,[],[50,56,63,70,77,84],{"skillNo":51,"name":52,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":19},"01M7AZRGQ6MPY5YSW2Q5AQ4SG5","prompts","https:\u002F\u002Fgithub.com\u002FMr-Shine09\u002FZephyr\u002Fblob\u002Fcompanion\u002Fvibe\u002Fcore\u002Ftools\u002Fbuiltins\u002Fprompts\u002Fskill.md",[],[],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M7AZRCBR2K5DR24TJBKVF9W0","write-vibe-tests","Write or refactor Mistral Vibe tests with proper decoupling. Use when adding behavior coverage, testing ports\u002Fadapters, replacing brittle mocks, creating fakes, adding characterization tests before refactors, or changing tests under tests\u002F for vibe\u002Fcore, vibe\u002Fcli, vibe\u002Facp, tools, config, sessions, skills, hooks, MCP, or setup.","https:\u002F\u002Fgithub.com\u002FMr-Shine09\u002FZephyr\u002Fblob\u002Fcompanion\u002F.vibe\u002Fskills\u002Fwrite-vibe-tests\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7AZR8NPPAHVP4EVJG8H07SF","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\u002Fadr or AGENTS.md must be changed.","https:\u002F\u002Fgithub.com\u002FMr-Shine09\u002FZephyr\u002Fblob\u002Fcompanion\u002F.vibe\u002Fskills\u002Fwrite-vibe-adr\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7AZR33WNNYXT1P8AK6NDAWS","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.","https:\u002F\u002Fgithub.com\u002FMr-Shine09\u002FZephyr\u002Fblob\u002Fcompanion\u002F.vibe\u002Fskills\u002Finstrument-feature-analytics\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7AZQZJBG6FH0RP5QR9RAWP9","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\u002Fcore, vibe\u002Fcli, vibe\u002Facp, vibe\u002Fsetup, built-in tools, config, sessions, skills, hooks, MCP, connectors, or other Vibe feature code.","https:\u002F\u002Fgithub.com\u002FMr-Shine09\u002FZephyr\u002Fblob\u002Fcompanion\u002F.vibe\u002Fskills\u002Fcreate-vibe-feature\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7AZQWCSN5MYHFEKHVXYCW7X","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.","https:\u002F\u002Fgithub.com\u002FMr-Shine09\u002FZephyr\u002Fblob\u002Fcompanion\u002F.agents\u002Fskills\u002Fvibe-textual-ui\u002FSKILL.md",[],[]]