Repository navigation
Closed
Labels
enhancementNew feature or requestNew feature or requestin-progressIssue is being actively worked onIssue is being actively worked onrecipe:implementationRoute through implementation recipeRoute through implementation recipe
Description
Maintainer setup
None beyond #5230. This test makes no model calls: no MiniMax, Anthropic or OpenAI key is used.
What it proves
A user installing AutoSkillit from scratch gets a working, self-consistent installation: in a fresh user container, autoskillit install succeeds and autoskillit doctor then reports no ERROR results.
Expected to fail today
Observed 2026-10-03 in a fresh container from the prototype image (AutoSkillit 0.10.1248, Claude Code 2.1.280):
autoskillit installexited 0 and printedPlugin published: autoskillit@autoskillit-local (scope: user), yetautoskillit doctorthen reportedautoskillit not registered,Plugin cache directory missing,Missing hooksandHook registry has changed since last install. Run 'autoskillit install'.- Two ERROR results:
installation_record_invalid(RECORD path../../../bin/autoskillit, from the image's splitUV_TOOL_DIR/UV_TOOL_BIN_DIRlayout — check) andsecret_scanning_hook(no.pre-commit-config.yamlin the empty working directory). autoskillit doctorexited 0 despite those errors: the command never derives an exit status from severity (command). The test must gate on the JSON output, not the exit code.
Each real defect this test exposes gets its own bug issue; the test lands in the catalog marked expected-failure with a link to that bug until it is fixed.
Scope
- Catalog entry: no LLM, runs whenever the selector picks it (cheap enough to also run on every PR touching
src/autoskillit/cli/,src/autoskillit/workspace/orscripts/docker/). - Steps: fresh container (no home volume) →
autoskillit install→autoskillit initin a scratch git repository with a pre-commit config →autoskillit doctor --output-json. - Assertion: zero
errorresults; each allowedwarningis listed explicitly in the test with the reason it is expected.
Acceptance criteria
- The test runs in CI in the
userimage and gates on doctor's JSON. - Every ERROR it reports today is either fixed or linked to an open bug.
Metadata
Metadata
Assignees
Labels
enhancementNew feature or requestNew feature or requestin-progressIssue is being actively worked onIssue is being actively worked onrecipe:implementationRoute through implementation recipeRoute through implementation recipe
Activity