commitlisted

# Commit Skill Analyze code changes, group them into logical packages where appropriate, to create sequential, clear, descriptive commits with effective titles and detailed descriptions. --- ## Levels of Detail | Level | Component | Purpose | |-------|-----------|---------| | **Highest** | Title | Single sentence capturing all changes comprehensively yet succinctly | | **Middle** | Description | One level deeper - enough to fully understand without viewing files | | **Lowest** | Files | The actual diff - reader can inspect directly if needed | --- ## Step 1: Grouping Analyze all changes and determine commit packages. **Grouping Priority:** | Priority | Criterion | Example | |----------|-----------|---------| | 1 | Feature cohesion | All files for user auth feature | | 2 | Directory scope | All changes in `auth/` module | | 3 | Logical separation | Config changes separate from code | | 4 | Dependency order | Interface before implementation | **Split Decision:** - Can describe in one sentence? �� Single commit - Multiple unrelated changes? → Split by concern - Too complex for one sentence? → Split by logical phase **Commit Sequence (when splitting):** - What change enables or defines the others? → Commit first - Would a reviewer understand each commit in isolation? - Does the sequence tell a coherent story? - Order so earlier commits provide context for later ones --- ## Step 2: Title Write one sentence that: - Captures ALL changes at the highest level - Is concis