Name: Manage Commits
Author: androidx

Manage Commits Skill

This skill enforces AndroidX-specific rules and conventions when creating or modifying commits in the support/ project.

AndroidX Commit Rules

Run ktlint First: Before creating or amending a commit, you must always run ktlint on all modified .kt files to prevent build failures, using the exact command: ./gradlew :ktCheckFile --format --file <file> Resolve any issues that arise before proceeding.
Describe Change and Rationale: The commit message must clearly describe what the change does and the rationale behind it.
Test Stanza Required: ALL commits must have a Test: stanza detailing what tests cover the change.
- If the change does not require tests (e.g., a markdown-only change), you must still include the stanza with a rationale explaining why it doesn't need tests (e.g., Test: markdown file change only).

This skill enforces AndroidX-specific rules and conventions when creating or modifying commits in the support/ project.

Run ktlint First: Before creating or amending a commit, you must always run ktlint on all modified .kt files to prevent build failures, using the exact command: ./gradlew :ktCheckFile --format --file <file> Resolve any issues that arise before proceeding.
Describe Change and Rationale: The commit message must clearly describe what the change does and the rationale behind it.
Test Stanza Required: ALL commits must have a Test: stanza detailing what tests cover the change.
- If the change does not require tests (e.g., a markdown-only change), you must still include the stanza with a rationale explaining why it doesn't need tests (e.g., Test: markdown file change only).