Context
All configuration is via CLI flags only. There is no config file. Users running pulser in CI or across multiple repos have to repeat flags every time:
pulser --strict --all --format json
Proposed solution
Support a .pulserrc.json config file:
{
"strict": true,
"all": true,
"format": "json",
"path": ".claude/skills"
}
Lookup order:
.pulserrc.json in current directory
~/.pulserrc.json as global fallback
- CLI flags always override config file
What to do
- Create
src/config.ts with a loadConfig() function
- Modify
src/index.ts to merge config with CLI opts before calling run()
- The
CLIOptions type in src/types.ts already defines the shape — reuse it
Files to modify
- New:
src/config.ts
src/index.ts (merge logic)
Difficulty: Easy-Medium
Context
All configuration is via CLI flags only. There is no config file. Users running pulser in CI or across multiple repos have to repeat flags every time:
Proposed solution
Support a
.pulserrc.jsonconfig file:{ "strict": true, "all": true, "format": "json", "path": ".claude/skills" }Lookup order:
.pulserrc.jsonin current directory~/.pulserrc.jsonas global fallbackWhat to do
src/config.tswith aloadConfig()functionsrc/index.tsto merge config with CLI opts before callingrun()CLIOptionstype insrc/types.tsalready defines the shape — reuse itFiles to modify
src/config.tssrc/index.ts(merge logic)Difficulty: Easy-Medium