Name: .github
Author: vanillagreencom

Imported from vanillagreencom/kendex (.github/AGENTS.md). Install upstream with npx skills add vanillagreencom/kendex --skill .github. Copyright stays with the author.

.github/

This repository's own continuous integration and the instruction files its review bots read. Nothing here is catalog content.

copilot-instructions.md, instructions/code-review.md and instructions/*.instructions.md are rendered by the bot-instructions package and each names its generator in a comment: line 1 of the first two, and below the applyTo frontmatter in an instructions/*.instructions.md. Change [bot-instructions] in the effective manifest and re-render, never the file.
instructions/code-review.md is this repository's whole review doctrine. AGENTS.md § Code Review Rules is the directive line that sends Codex there, and copilot-instructions.md carries the same pointer for Copilot.
Every job runs on a GitHub-hosted runner. This repository is public and declares no self-hosted runner; the two publish workflows read vars.CI_RUNNER_2V for the fleet's runner and fall back to ubuntu-latest, which is what runs here since the variable is unset.
own-catalog.yml holds this repository to the same check a consumer gets by calling catalog-check.yml, which is the reusable workflow consumers call; keep the caller's content out of the reusable one.
skill-tests.yml is the suite runner ../skills/AGENTS.md names; it carries the tools/ and hooks/ suites and the Bash 3.2 legs as well. Its changes job reads the change class once through actions/change-class, and ../tools/ci-job-set turns that class into the lane selection every gated job reads, in its own condition or, for the platform legs, in the shard matrix. The aggregators keep the required contexts present through ../tools/ci-aggregate, which accepts a skipped lane only where the class authorized it. The Preflight (diff-scoped deterministic checks) and Markdown (format + references) jobs are required checks on pull requests and skip merge groups.
actions/change-class is the composite action this repository's workflows read a change class from, and the one a consumer references as vanillagreencom/kendex/.github/actions/change-class@main in place of calling its vendored classifier, per ../skills/harness-ci/references/wiring.md § Through the composite action. It wraps ../skills/harness-ci/scripts/change-class and harness-only --mode docs and classifies nothing itself; its suite is ../tools/tests/change-class-action.test.sh. Its classifier input names the checkout the shipped scripts are read from, and skill-tests.yml passes a separate default-branch checkout, so the classifier and the orch contract it measures by are never the pull request's copies. The wrapper itself, tools/ci-job-set and tools/ci-aggregate do run from the pull request's tree: review holds them, and a change to any of them is refused every narrow class, so it runs every lane. A change to the classifier is proved by the harness-ci suite.
review-gate-writer.yml is a relay whose body must equal the review-gate package's template, which ../skills/review-gate/scripts/validate-workflow.sh checks.
release.yml is ../docs/RELEASING.md.
publish-aur.yml and publish-homebrew.yml carry packaging/ to the AUR and the Homebrew tap; triggers, the dry-run dispatch and the secrets each needs are ../packaging/README.md § Publishing. Neither is called by release.yml: a release is published as a draft and the recipe bump follows it.

Install .github and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

{ "ocm": "1", "id": "vanillagreencom-kendex-github", "kind": "skill", "name": ".github", "description": "This repository's own continuous integration and the instruction files its review bots read. Nothing here is catalog content.", "publisher": "vanillagreencom", "version": "1.0.0", "capabilities": { "domains": [ "coding", "data_analysis" ], "tags": [ "skill-md", "github-agents" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "This repository's own continuous integration and the instruction files its review bots read. Nothing here is catalog content." ], "primary": false, "metadata": { "source": { "provider": "github-agents", "repository": "https://github.com/vanillagreencom/kendex", "path": ".github/AGENTS.md", "ref": "8390173dbe02c160b7e3fa16d7bf237cf62085e1", "url": "https://github.com/vanillagreencom/kendex/blob/8390173dbe02c160b7e3fa16d7bf237cf62085e1/.github/AGENTS.md", "key": "vanillagreencom/kendex/.github/AGENTS.md" } }, "instructions": "# .github/\n\nThis repository's own continuous integration and the instruction files its review bots read. Nothing here is catalog content.\n\n- `copilot-instructions.md`, `instructions/code-review.md` and `instructions/*.instructions.md` are rendered by the bot-instructions package and each names its generator in a comment: line 1 of the first two, and below the `applyTo` frontmatter in an `instructions/*.instructions.md`. Change `[bot-instructions]` in the effective manifest and re-render, never the file.\n- `instructions/code-review.md` is this repository's whole review doctrine. `AGENTS.md` § C", "cost": { "context_tokens": 925 } }

.github

About

.github/

Install .github and it becomes one more candidate the router can pick - when it fits.

Use it

Manifest

Reviews