Skip to content
Raw Markdown

Add the context files

Keep the context in a repository so people and coding agents can review and maintain the same files.

For your first question on a small set of tables, follow Build and publish your first context. It includes the source preparation, agent prompt, review and publication steps.

Pull an existing context

Install and authenticate the CLI, then open your repository and pull the project:

cassis context pull --project <project-id>
cassis schema pull
cassis context fmt
cassis context check

Pull writes the context files, cassis/project.yml and the generated cassis/AGENTS.md modeling guide. The schema pull writes a local snapshot for your agent to read. Review the files and commit the context before making further changes.

Start a larger context

The context bootstrap kit assembles a first context from your schema, dbt models, dashboards and documentation. Use it when you want to recover definitions across a larger set of sources. It keeps evidence with its findings and asks you to review the scope, domain grouping, metrics and unresolved business questions.

The kit can run on local exports without a Cassis account. You can use the generated files independently or connect them to a Cassis project when you want to publish there.

Install the skill and point your coding agent at the source files using the kit’s getting-started instructions. The kit runs separately from the Cassis CLI and produces a context tree for review. If you choose to publish in Cassis, follow its integration instructions to bind that tree to your project, validate it and commit it before uploading.

If you already have reviewed context, use Expand your context instead. The bootstrap kit generates a new tree; it does not merge additions into an existing one.

To author files directly, use the minimal example and the modeling guide generated by the CLI. Preserve the project.yml that binds your checkout to the intended project.

Publish a reviewed context

For a project without an automated publisher, commit the complete context and upload it:

cassis context fmt
cassis context check
git add -- cassis
git diff --cached -- cassis
git commit -m "Add reviewed Cassis context"
cassis context upload
cassis status

The upload publishes the context. On a never-published project, this becomes version 1. Check that the published commit matches your checkout.

An upload replaces the whole context. Keep supporting documents outside the configured cassis/ path, and use an Editor key whose domain access covers the root. If the GitHub App already publishes this project, use its workflow instead of adding a second publisher.

For later changes, choose how merges publish and follow Curate a git-managed project.