docs: update README — all current commands and configuration#47
docs: update README — all current commands and configuration#47greynewell merged 1 commit intomainfrom
Conversation
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
WalkthroughThe README was restructured from a marketing-focused layout to a command-centric guide. It now explicitly documents two operational modes (file mode and on-demand analysis), provides quickstart instructions with CI-friendly authentication, lists command categories with their purposes, and includes detailed configuration and integration setup for Claude Code and MCP. Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
There was a problem hiding this comment.
🧹 Nitpick comments (1)
README.md (1)
108-123: Configuration section is accurate.The documented environment variables (
SUPERMODEL_API_KEY,SUPERMODEL_API_BASE,SUPERMODEL_FILES) match the implementation ininternal/config/config.go. The CI example on lines 119-123 gives a practical, copy-paste-ready snippet.One minor observation: the
outputfield on line 115 shows valid values (human | json) but doesn't mention an environment variable override, while the other fields do. This is actually correct—there's noSUPERMODEL_OUTPUTenv var in the code—but you might consider adding a brief note like "# human | json (no env override)" to make the formatting more consistent with the other fields and avoid any user confusion.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@README.md` around lines 108 - 123, Update the README Configuration block to clarify that the "output" setting does not have an environment-variable override: revise the `output: human # human | json` line to add a short note such as "(no env override)" so it matches the format used for other fields and avoids confusion; reference the `output` field in the README and the lack of `SUPERMODEL_OUTPUT` in internal/config/config.go when making this clarification.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Nitpick comments:
In `@README.md`:
- Around line 108-123: Update the README Configuration block to clarify that the
"output" setting does not have an environment-variable override: revise the
`output: human # human | json` line to add a short note such as "(no
env override)" so it matches the format used for other fields and avoids
confusion; reference the `output` field in the README and the lack of
`SUPERMODEL_OUTPUT` in internal/config/config.go when making this clarification.
Summary
factorycommand was removed andauditwas added.graph.*sidecar files) and on-demand analysis~/.supermodel/config.yamland all environment variablesTest plan
supermodel --helpoutputfactorycommandSUPERMODEL_API_KEY,SUPERMODEL_API_BASE,SUPERMODEL_FILES) matchinternal/config/config.gosupermodel hook --helpdescriptionsupermodel mcp --helpexample🤖 Generated with Claude Code
Summary by CodeRabbit