메뉴
Produce a commit subject, branch name, and PR title that match Chai's conventions. Triggered by "commit-convention", "/commit-convention", "write a commit message", or by the gitter agent before committing or opening a PR.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | commit-convention |
| description | Produce a commit subject, branch name, and PR title that match Chai's conventions. Triggered by "commit-convention", "/commit-convention", "write a commit message", or by the gitter agent before committing or opening a PR. |
You turn a set of changes into a correctly-formatted commit subject, branch name, and PR title. You draft text; the gitter agent or the user runs the git commands.
feat:, fix:).Co-Authored-By trailer.Good: Added CCard elevation token · Fixed primary button container color · Updated dependencies to latest versions
Bad: feat: add card · Fixes the button. · update stuff
1–3 files, split by dependency layer: tokens/atoms → components → theme wiring → demo → tests → docs. One documentation .md file per commit — never bundle multiple docs. If the change spans layers, propose multiple commits with a subject each.
feature/<slug>, fix/<slug>, or docs/<slug> — lowercase, hyphenated. Example: feature/ccard-elevation.
Same style as the commit subject (past tense, no prefix/period). PRs target develop.
Branch: feature/<slug>
Commits:
1. <subject> (files: …)
2. <subject> (files: …)
PR title: <title> (base: develop)
If the staged/working changes don't justify splitting, output a single commit. Read the actual diff (git diff) before drafting — base the subject on what changed, not on the request wording.
Write or extend tests for the Chai repo. Triggered by "write a test", "add tests", "test this", or as the follow-up when a component/util lands without coverage. Local unit tests use JUnit 6 (Jupiter); Compose/UI behaviour is tested as instrumented tests. Picks the right source set and idioms; does not invent mocking/assertion libraries the catalog does not declare.
Find design-system violations in Chai source — raw Material components, hardcoded colors, bare .dp magic numbers, @Preview instead of @ChaiPreview. Triggered by "audit-design-system-usage", "/audit", or by checks/code-reviewer. This is the check the broken chailinter is meant to do. Reports; does not edit.
Verify the Chai project assembles. Triggered by "check-build", "/check-build", "does it build", or by checks as the assemble gate. Runs `./gradlew assembleDebug` only — no mutation, no formatting.
Run Android Lint on Chai and report. Triggered by "check-lint", "/check-lint", "run lint", or by checks as the lint gate. Runs `./gradlew lintDebug` only — reports the first violation, never edits.
Umbrella pre-PR gate for Chai. Triggered by "checks", "/checks", "run the checks", or by any agent that needs a green light before committing or opening a PR. Runs the design-system audit, Android Lint, unit tests, and a debug assemble, then reports a single pass/fail.
Update gradle/libs.versions.toml toward latest stable and verify safely. Triggered by "dependency-bump", "/dependency-bump", "update dependencies", "bump versions". Follows the dependency checklist in docs/tech/findings.md.