Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
41 commits
Select commit Hold shift + click to select a range
51050d5
feat: project health: new DataPilot insights on the models Claude cha…
hkaltai Nov 13, 2026
45c795f
fix: project health band updates
hkaltai Nov 13, 2026
f3d172b
Merge feat/pu-mods-foundation into feat/health
hkaltai Nov 13, 2026
fd340eb
fix: project health push gate holds on an unfinished or failed check,…
hkaltai Nov 13, 2026
a21c1c8
fix: push gate reads heredocs, here-strings and unbalanced substituti…
hkaltai Nov 13, 2026
53bea56
fix: a heredoc belongs to the command it follows, and a shift is not …
hkaltai Nov 13, 2026
40deecc
fix: the health push gate sees a push behind a leading redirect, skip…
hkaltai Nov 14, 2026
beb0583
fix: the health check skips models inside an installed dbt package th…
hkaltai Nov 14, 2026
3538583
fix: the health push gate sees a push behind a leading input redirect…
hkaltai Nov 14, 2026
d4020f9
fix: an input redirect's file is read, not written, and quoted digits…
hkaltai Nov 14, 2026
2b0ce1c
fix: the health hooks resolve symlinked folders through the engine, s…
hkaltai Nov 15, 2026
73660d7
fix: health commits a check only once every edited file's folder is r…
hkaltai Nov 15, 2026
00f366a
fix: a health check from before a session restart writes nothing whil…
hkaltai Nov 15, 2026
de85ff6
fix: the health feature clears a status part an earlier process left,…
hkaltai Nov 15, 2026
c26b3f0
Merge remote-tracking branch 'origin/feat/pu-mods-foundation' into fe…
hkaltai Nov 17, 2026
c40f3b9
test: health's feature tests on top of the foundation's registration …
hkaltai Nov 17, 2026
6a872c6
Merge commit '4c8add5238faa61034cf3a21037c50d77eb9db32' into feat/health
hkaltai Nov 17, 2026
00c9161
fix: the health push gate answers inside the tool chain's deadline, a…
hkaltai Nov 17, 2026
f7ad7ad
fix: the health push gate counts its earlier work against the chain's…
hkaltai Nov 17, 2026
5d1f513
fix: a deleted shared schema file counts every model, those without a…
hkaltai Nov 17, 2026
3cce2c0
fix: the health push gate measures its remaining wait after its last …
hkaltai Nov 17, 2026
657293b
Merge remote-tracking branch 'origin/feat/pu-mods-foundation' into fe…
hkaltai Nov 17, 2026
cc4d687
fix: project health keeps the baseline when no schema file is named, …
hkaltai Nov 17, 2026
59f84f2
fix: project health treats a result the engine cut at its size limit …
hkaltai Nov 17, 2026
f8104bd
docs: project health states what it cannot see of a shell's working f…
hkaltai Nov 17, 2026
eb08fe7
fix: project health settings and README say the check is live, a nest…
hkaltai Nov 17, 2026
a9adab2
Merge remote-tracking branch 'origin/main' into feat/health
hkaltai Nov 17, 2026
4d2b7d5
Keep to health's own files: shared files match main; health bounds it…
hkaltai Nov 17, 2026
bbac474
test(health): pin the push gate's wait below the tool chain's phase d…
hkaltai Nov 18, 2026
ce2011c
fix(health): a model dropped from a schema file that still documents …
hkaltai Nov 18, 2026
9962fac
fix(health): bound the whole push-gate decision, folder lookups inclu…
hkaltai Nov 18, 2026
49266f7
Merge origin/main into feat/health
hkaltai Nov 18, 2026
01378cb
fix(health): a comment no longer hides a push, a throwing clock drops…
hkaltai Nov 18, 2026
5c13dd1
docs(health): state the late-baseline limit for a model dropped from …
hkaltai Nov 18, 2026
eb8d48c
fix(health): a relative file a Bash command writes is read from the s…
hkaltai Nov 18, 2026
ee73986
fix(health): a cd in the same Bash command is read from the folder th…
hkaltai Nov 18, 2026
f04ebc7
test(health): the push gate reads a relative edit from the shell's fo…
hkaltai Nov 18, 2026
9b9b05a
test(health): pin the shell folder the push gate reads a relative edi…
hkaltai Nov 18, 2026
1aa54d6
fix(health): the shell-folder lookup of a push is inside the gate's b…
hkaltai Nov 18, 2026
f352d99
fix(health): the shell folder noted before a command belongs to that …
hkaltai Nov 18, 2026
ee9b55a
Merge origin/main into feat/health
hkaltai Nov 18, 2026
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions plugins/altimate-code/.claude-plugin/plugin.json
Original file line number Diff line number Diff line change
Expand Up @@ -31,14 +31,14 @@
},
"healthBlocksPush": {
"type": "boolean",
"title": "Project health blocks git push (not used yet)",
"description": "Not used yet: the project health check isn't in this version, so git push is never refused. When it ships, on refuses a push while the check finds new issues in the models you changed; off only shows them.",
"title": "Project health blocks git push",
"description": "On refuses a git push while the project health check finds new issues in the models you changed this session; off only shows them.",

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Minor (wording; Codex found it). This says a push is refused "while the project health check finds new issues". After a model change, the gate also refuses when the check failed, did not finish within the 4 s wait, or has no baseline yet, even with zero issues (health.tsx:728). The README row at line 144 has the same gap. Adding one clause would match the code. It does not block, because the refusal text tells the user why.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Agreed; the plugin.json and README wording will state that the push is also refused when the check failed, timed out or has no baseline. Follow-up PR.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Already matches at main: plugin.json and the README row say the push is also held while the check cannot run or has not finished.

"default": false
},
"healthConfigPath": {
"type": "string",
"title": "Project health check config",
"description": "Not used yet: the project health check isn't in this version. Path to a DataPilot health check config file, relative to the dbt project. Empty uses the default checks.",
"description": "Path to a DataPilot health check config file, relative to the dbt project. Empty uses the default checks.",
"default": ""
},
"commentsPollSeconds": {
Expand Down
6 changes: 3 additions & 3 deletions plugins/altimate-code/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -52,7 +52,7 @@ If altimate-code is not on PATH or not configured, the plugin surfaces the failu
1. A **SessionStart hook** adds a description of the available tools and both modes to the session, and copies the linked workspace's skills (see below). It does not start the MCP server. In a linked project, the [team rules](#team-rules) hooks add the workspace's rules too.
2. **MCP mode.** Claude calls `warehouse_list`, `warehouse_add`, `sql_execute` (`tables` returns columns and value profiles; large results spill to a local file), `sql_materialize` (session-local `scratch` DuckDB for cross-database joins), `answer_commit`, and `impact_analysis`, `dbt_lineage`, `altimate_core_column_lineage`, `schema_detect_pii`, `data_diff`, `altimate_core_equivalence`, `sql_translate`.
3. **CLI mode.** The **skill** has Claude run `altimate tool context` once (connections, schema listing, analyst method), then `altimate tool run <name> --args '<json>'` through Bash and reason over the structured output. `altimate tool list --json` shows every tool and its input schema. A warm process per project starts automatically.
4. Calls are read-only unless you approve `--allow-write` (CLI mode); `DROP DATABASE`, `DROP SCHEMA` and `TRUNCATE` are always blocked. Read-only is enforced by the database on Postgres, SQLite and DuckDB and by SQL classification elsewhere, so use a read-only DB user for the strongest boundary.
4. Calls are read-only unless you approve `--allow-write` (CLI mode), except the project health check: it runs `dbt_health` with write, without asking, because the dbt project's integration refreshes `target/` (and runs `dbt deps`), so it starts only in an interactive session (or with `healthBlocksPush` on) that is inside a dbt project, and has no separate off switch; `DROP DATABASE`, `DROP SCHEMA` and `TRUNCATE` are always blocked. Read-only is enforced by the database on Postgres, SQLite and DuckDB and by SQL classification elsewhere, so use a read-only DB user for the strongest boundary.
5. For long multi-step jobs, or when you invoke **`/altimate-code:altimate <task>`** for work that needs the agent, Claude Code runs `altimate run "<your task>"` locally with the `builder` agent (or `analyst` for a data question when MCP is unavailable), which uses your configured LLM provider.
6. Warehouse queries and dbt commands run **locally under your credentials**. If the installed CLI predates the `tool` subcommand, the skill falls back to delegation.

Expand Down Expand Up @@ -136,12 +136,12 @@ Rule drafting uses altimate-code's own model (sign in to the Altimate LLM Gatewa

## Settings

The plugin has five settings, shown when you enable it (`userConfig` in `.claude-plugin/plugin.json`). None is used yet: the features that read them are not in this version, so changing one changes nothing. The table says what each will control.
The plugin has five settings, shown when you enable it (`userConfig` in `.claude-plugin/plugin.json`). `healthBlocksPush` and `healthConfigPath` are used by the project health check. `maxScanBytes` and the comments settings are not used yet: the features that read them are not in this version, so changing one changes nothing. The table says what each controls.

| Setting | Default | What it controls |
| --- | --- | --- |
| `maxScanBytes` | 10 GiB | The largest BigQuery scan a dbt run, build or show may make before it waits for your approval (0 never waits; at least 0). Other warehouses are never held. |
| `healthBlocksPush` | off | When on, `git push` is refused while the project health check finds new issues in the models you changed. Off, the issues are only shown. |
| `healthBlocksPush` | off | When on, `git push` is refused while the project health check finds new issues in the models you changed. Off, the issues are only shown. If the first check of a session lands after you changed a model, that model's existing issues count as new (the baseline then lacks them). The reverse also holds: a model you drop from a schema file before that first check lands has its new issues taken as existing, so a push is not held for them. |
| `healthConfigPath` | empty | The DataPilot health check config file, relative to the dbt project. Empty uses the default checks. |
| `commentsPollSeconds` | 900 | How often the team's comments on shared docs are fetched again (at least 30). |
| `commentsInContext` | on | Whether the open comments on a model Claude reads or edits are added to its context. |
Expand Down
3 changes: 3 additions & 0 deletions plugins/altimate-code/hooks/features/docs.test.tsx
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,7 @@ import { expect, mock, test } from 'claude-code/testing'

import { PHASE_TIMEOUT_MS } from '../tool-chain'
import { ROUND_MS, applyPrompt, candidatesFrom, changedDescriptions, columnDescriptions, modelPaths, sentGroups } from './docs'
import { nothingToReport } from '../inert-features'

const ROOT = '/repo'
const MANIFEST_PATH = `${ROOT}/target/manifest.json`
Expand Down Expand Up @@ -257,6 +258,8 @@ async function start($: any, on: any, options: Options = {}) {
on('process.run', (_: unknown, e: { argv: readonly string[] }) => {
const [, command, , tool] = e.argv
if (command !== 'tool' || tool === 'docs_share_comments') return { value: { exitCode: 1, stdout: '', stderr: 'not this test' } }
// The project health check asks for its own tool at session start: not a call this feature makes.
if (tool === 'dbt_health') return { value: nothingToReport(e.argv)! }
calls.push(`cli:${tool}`)
toolArgs.push(String(e.argv[5]))
if (tool === 'dbt_docs_coverage') {
Expand Down
Loading
Loading