Problem
Running agentready bootstrap generates the repomix-update.yml GitHub Actions workflow, but does not create repomix.config.json or .repomixignore. This means the workflow is in place to keep repomix output fresh, but the initial configuration hasn't been done. A user who runs only bootstrap and then assess will see repomix_config fail with "not configured."
The expected user flow today requires three separate commands:
agentready repomix-generate --init (create config)agentready repomix-generate (generate initial output)agentready bootstrap (set up the automation workflow)
Proposal
Have agentready bootstrap also call repomix-generate --init (config + ignore file creation) as part of its workflow generation step. This way, after a single bootstrap command, the repo has both the configuration and the automation in place. The user would only need to run agentready repomix-generate afterward to produce the initial output (or let the workflow handle it on the next push to main).
Generating the actual repomix output during bootstrap is probably out of scope since it requires repomix (a Node.js tool) to be installed, and bootstrap should not assume that.
Acceptance criteria
agentready bootstrap creates repomix.config.json and .repomixignore alongside the workflow- Existing
repomix.config.json is not overwritten if already present
agentready assess after bootstrap reports repomix_config as "configured but no output" (score 50) rather than "not configured" (score 0)- Unit tests updated to verify config file generation
Submitted by Bill Murdock with assistance from Claude Code.
Problem
Running
agentready bootstrapgenerates therepomix-update.ymlGitHub Actions workflow, but does not createrepomix.config.jsonor.repomixignore. This means the workflow is in place to keep repomix output fresh, but the initial configuration hasn't been done. A user who runs onlybootstrapand thenassesswill seerepomix_configfail with "not configured."The expected user flow today requires three separate commands:
agentready repomix-generate --init(create config)agentready repomix-generate(generate initial output)agentready bootstrap(set up the automation workflow)Proposal
Have
agentready bootstrapalso callrepomix-generate --init(config + ignore file creation) as part of its workflow generation step. This way, after a singlebootstrapcommand, the repo has both the configuration and the automation in place. The user would only need to runagentready repomix-generateafterward to produce the initial output (or let the workflow handle it on the next push to main).Generating the actual repomix output during bootstrap is probably out of scope since it requires
repomix(a Node.js tool) to be installed, and bootstrap should not assume that.Acceptance criteria
agentready bootstrapcreatesrepomix.config.jsonand.repomixignorealongside the workflowrepomix.config.jsonis not overwritten if already presentagentready assessafter bootstrap reportsrepomix_configas "configured but no output" (score 50) rather than "not configured" (score 0)Submitted by Bill Murdock with assistance from Claude Code.