Skip to content

feat: preflight_init tool + .preflight/ config directory (#9) - #68

Closed
TerminalGravity wants to merge 1 commit into
mainfrom
feat/preflight-config-dir
Closed

feat: preflight_init tool + .preflight/ config directory (#9)#68
TerminalGravity wants to merge 1 commit into
mainfrom
feat/preflight-config-dir

Conversation

@TerminalGravity

@TerminalGravity TerminalGravity commented Mar 3, 2026

Copy link
Copy Markdown
Collaborator

Closes #9

  • New preflight_init tool scaffolds .preflight/ with config.yml, triage.yml, rules.md, patterns.json, contracts/
  • loadPatterns() merges version-controlled patterns with auto-generated ones
  • loadRules() surfaces rules.md in preflight_check output
  • New test suite (48 tests passing)
  • Tool count: 24 → 25

)

- New preflight_init tool scaffolds .preflight/ directory with config.yml,
  triage.yml, rules.md, patterns.json, and contracts/ directory
- loadPatterns() now merges version-controlled .preflight/patterns.json
  with auto-generated patterns (manual patterns take precedence by id)
- loadRules() reads .preflight/rules.md and surfaces it in preflight_check
  output for non-trivial prompts
- preflight_check now shows project rules section when rules.md exists
- Added test suite for .preflight/ config directory structure
- Tool count: 24 → 25
@TerminalGravity
TerminalGravity force-pushed the feat/preflight-config-dir branch from 30c6f1e to be8c525 Compare March 3, 2026 17:46
@TerminalGravity TerminalGravity changed the title feat: complete .preflight/ config directory support feat: preflight_init tool + .preflight/ config directory (#9) Mar 3, 2026

@TerminalGravity TerminalGravity left a comment

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewed — this is a clean implementation of #9. The scaffolding approach is smart: giving users a starting point with config.yml, triage.yml, rules.md, and patterns.json without being opinionated about how they use it. The merge logic in loadPatterns() correctly prioritizes manual patterns by id while preserving the higher frequency count — nice touch. loadRules() integration into preflight_check is straightforward.

One thing to note: the node engine bump from >=18 to >=20 in package-lock.json is worth calling out in release notes since it's technically a breaking change for anyone on Node 18.

CI green, 48 tests passing. Ready to merge.

@TerminalGravity

Copy link
Copy Markdown
Collaborator Author

Superseded by newer PRs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

.preflight/ project config directory

1 participant