Expand description
Context data structures for enhanced commit message analysis.
Structs§
- Branch
Context - Branch analysis and work pattern detection.
- Commit
Context - Complete context information for intelligent commit message improvement.
- Commit
Range Context - Multi-commit analysis and work patterns.
- Commit
Rules - Deterministic commit-message lint configuration.
- Feature
Context - Context for a specific feature or work area.
- File
Context - File-based context and architectural understanding.
- Project
Context - Project-level context discovered from configuration files.
- Project
Conventions - Project conventions parsed from documentation.
- Scope
Analysis - Analysis of scope consistency across commits.
- Scope
Definition - Definition of a valid scope in the project.
- Scope
Requirements - Requirements and validation rules for commit scopes.
Enums§
- Architectural
Impact - Impact on system architecture.
- Architectural
Layer - Architectural layer of the file.
- Change
Impact - Impact of changes to this file.
- Change
Significance - Significance of changes for commit message detail level.
- Ecosystem
- Detected project ecosystem.
- File
Purpose - Purpose of the file in the project.
- Project
Significance - Significance of file in project.
- Verbosity
Level - Suggested level of detail for commit messages.
- Work
Pattern - Detected work pattern across commits.
- Work
Type - Type of work being performed.
Constants§
- DEFAULT_
COMMIT_ TYPES - The ten conventional-commit types accepted by default when no
.omni-dev/commit-rules.yamloverrides them; mirrors the## Typestable in.omni-dev/commit-guidelines.md. - DEFAULT_
FORBIDDEN_ FOOTERS - Footer prefixes rejected by default (case-insensitive,
<prefix>:match). - DEFAULT_
SUBJECT_ MAX_ LEN - Default subject-line length limit (characters) used when no
.omni-dev/commit-rules.yamloverrides it.