Repository navigation
feat(cli): aexp init writes the config in one command (story 29.1) - #236
Merged
Merged
Conversation
aexp init [--print] [--force] [--verify <json array>] detects the project's test command (dotnet, npm, pytest, go; make test when nothing else fits), asks at a terminal when none or several fit, writes a commented .aexp/config.json, adds .aexp/ to .gitignore when under git, and prints the steps left to a person. It approves nothing: aexp trust stays theirs. aexp setup claude-code writes its config through the same generator (ProjectInit), so there is one. Review round 1 (edge cases): make test is a fallback so setup's detection is unchanged for the four old kinds; under-git walks up the parents; the Makefile regex excludes ::= assignments; init and setup refuse --config and report write failures without a stack trace. Co-Authored-By: Claude Fable 5.1 <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
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.
Story 29.1 of Epic 29 (Reach Without a .NET Toolchain).
aexp init [--print] [--force] [--verify <json array>], run in the project root:dotnet test,npm test,pytest,go test ./...;make testonly when none of those fits), asks at a terminal when none or several fit (a number, a JSON array, or Enter for the placeholder), or takes--verifyas a JSON array, never a shell line;.aexp/config.jsonwith today's defaults (atomic,.aexp/0700), never over an existing one without--force;.aexp/to.gitignorewhen the directory is under git (walking up for.git);aexp trust, thenaexp setup claude-codeorclaude mcp add. It approves nothing.aexp setup claude-codewrites its config and.gitignoreentry through the same generator, so there is one; its values are unchanged and the file is now commented. Both commands refuse--configand report a write failure without a stack trace.Tests:
AgentExperience.Cli.Tests129 passed (16 new inInitTests.cs, one per matrix row plus the acceptance criteria and a "every rendered config loads" theory). No lesson, holdout, hook or dogfood change.🤖 Generated with Claude Code