yapyak-commit
/yapyak-commit
Commit messages: the area-prefix form, the closed area table, subject and body rules, the push ban. Use when writing a git commit message or asked to commit.
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 15.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Commit messages: the area-prefix form, the closed area table, subject and body rules, the push ban. Use when writing a git commit message or asked to commit.
Original author description
Commit messages: the area-prefix form, the closed area table, subject and body rules, the push ban. Use when writing a git commit message or asked to commit.
How it works
SKILL.md has no level-two headings · 41 lines, 184 words
SKILL.md preview
--- name: yapyak-commit description: "Commit messages: the area-prefix form, the closed area table, subject and body rules, the push ban. Use when writing a git commit message or asked to commit." metadata: internal: true --- ### Form `<area>: <subject>` — one space after the colon, nothing before the area. ### Area — derive from the changed paths | Path prefix | Area | | --- | --- | | `packages/<dir>/` | `<dir>` | | `docs/` | `docs` | | `e2e/` | `e2e` | | `examples/` | `examples` | | `.agents/` | `skills` | | `.github/workflows/` | `ci` | | anything else | `repo` | 2+ areas in one commit → the area with the most changed files; tie → `repo`. ### Subject - Imperative present, lowercase first letter. Code identifiers keep their casing. - No trailing period. - Whole line ≤ 72 characters; aim for ≤ 50. ``` ✓ yapyak: silence warnings in production browser bundles ✓ e2e: fail prod runs on yapyak console output ✗ Fixed prod warnings (past tense, no area) ✗ yapyak: Add info command. (capitalized, trailing period) ``` ### Body - Never write a body → put the user-facing note in `.changeset/*.md`. - Attribution trailers are forbidden — commits carry the author's own identity. ### Push Never run `git push` — the user pushes manually.
Versions
The database has no other skills named yapyak-commit.
Database snapshot: 13.11.2026 · package version 4a016c44a673 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100yapyak
yapyak, an i18n compiler with a small runtime: t() with the source string as the key, ICU plurals and selects, rich text, format.* for numbers, dates and lists, locale switching and persistence, yapyak.config.ts, translators, the yapyak CLI, and YAPnnnn diagnostics. Use when… - 100yapyak
yapyak, an i18n compiler with a small runtime: t() with the source string as the key, ICU plurals and selects, rich text, format.* for numbers, dates and lists, locale switching and persistence, yapyak.config.ts, translators, the yapyak CLI, and YAPnnnn diagnostics. Use when… - 100commit-message
Generate conventional commit messages - use when creating commits, writing commit messages, or asking for git commit help - 100git-commit-message
Generates conventional-commit messages from staged changes: type prefix + English imperative subject (≤50 chars) + optional body explaining why. Use when the user asks to write, generate, or polish a git commit message. - 100yapyak-skill
The public agent skill in `skills/yapyak`: its layout, the change-to-edit table that keeps it current, and how its prose is written. Use when a change touches a public export, a config field, a CLI command, a diagnostic, an adapter, or guide content. - 100git-commit-message
Generates conventional-commit messages from staged changes: type prefix + English imperative subject (≤50 chars) + optional body explaining why. Use when the user asks to write, generate, or polish a git commit message.