feat: environment discovery before setup questions (user-defaults discovery half)#56
Merged
Merged
Conversation
…ct (#55) Step 0 preflight: read-only detection of git identity, gh auth/owner, SSH host aliases and existing profile/project config before any setup question; precedence user instruction -> project config -> detected tool state -> ask; one-line confirmation on detected values; accepted values state where they are recorded; secrets never stored (standard tools authoritative); multiple accounts/clusters ask, never assume. GitHub step 6 and the HPC step consume the discovery. The user.yaml defaults half stays deferred/evidence-gated. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #55.
Summary
start-new-project.mdgains step 0 — environment discovery, a lightweight preflight run before any setup question: read-only detection of git identity (git config), GitHub account/auth (gh auth status,gh api user), SSH host aliases (candidate HPC clusters), and the existing profile/project configuration, under the explicit precedenceuser instruction → project configuration → detected standard-tool state → ask. Detected values are used with a one-line overridable confirmation; unknowns become one focused question; accepted values state where they'll be recorded. Secrets are never stored or echoed — standard tools stay authoritative, and multiple accounts/clusters always prompt a which-one question rather than assuming a global default. GitHub step 6 (owner) and the optional HPC step (detected aliases offered as candidates) now consume the discovery instead of asking cold.The machine-local
~/.config/autolens_assistant/user.yamlhalf of the original prompt stays deferred and evidence-gated (rescope decision 2026-07-10).Scripts Changed
None — skill documentation only (
skills/start-new-project.md).Validation
--check-citations: 91 files, 389 citations, 0 missing.Readiness
Heart YELLOW on the standing 6-reason set only (human-acked repeatedly 2026-07-10); docs-only, not on the library release train.
🤖 Generated with Claude Code