Implement Step3: team customization#3
Merged
Merged
Conversation
…ternal tool input - Add .riskcheck.yaml config file support with YAML loading - Constructor injection for all signal config overrides (thresholds, weights, paths, test patterns) - riskcheck init command to generate config file - S-8: high_complexity signal via --complexity-file (external JSON) - S-9: low_coverage signal via --coverage-file (external JSON) - CLI flags: --config, --complexity-file, --coverage-file - Print errors to stderr before exit - Update specs, README with full feature documentation - 70+ unit tests across all packages Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
hidetzu
added a commit
that referenced
this pull request
May 4, 2026
…ternal tool input (#3) - Add .riskcheck.yaml config file support with YAML loading - Constructor injection for all signal config overrides (thresholds, weights, paths, test patterns) - riskcheck init command to generate config file - S-8: high_complexity signal via --complexity-file (external JSON) - S-9: low_coverage signal via --coverage-file (external JSON) - CLI flags: --config, --complexity-file, --coverage-file - Print errors to stderr before exit - Update specs, README with full feature documentation - 70+ unit tests across all packages
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.
Summary
.riskcheck.yamlconfig file support for team-specific scoring rulesriskcheck initcommand for config file generation--complexity-fileand--coverage-fileRelated Spec
specs/usecases.mdspecs/requirements.md(NFR-2 clarified)specs/spec.md(module structure, CLI flags, init command updated)specs/roadmap.mdRoadmap Step
Changes
internal/config: YAML config loading with pointer types for nil-safetyinternal/signal: All 7 existing signal constructors accept config injectioninternal/signal/high_complexity.go: S-8 — external complexity JSON inputinternal/signal/low_coverage.go: S-9 — external coverage JSON inputcmd/init.go:riskcheck initsubcommandcmd/root.go: Config loading, new flags, signal wiring with configmain.go: Error messages printed to stderr before exitREADME.md: Full feature documentation (signals table, config, external tools, exit codes).riskcheck.yaml.example: Sample config with all optionsDesign Decisions
initrefuses to overwrite existing configTest Plan
.riskcheck.yamloverrides default behavior