بنقرة واحدة
commit
Create a git commit with livery conventions — conventional commits with fe/be scope prefix
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
القائمة
Create a git commit with livery conventions — conventional commits with fe/be scope prefix
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use this skill to generate well-branded interfaces and assets for Black Atom Industries (incl. the Livery theme manager), either for production or throwaway prototypes/mocks/etc. Contains essential design guidelines, colors, type, fonts, and UI kit components for prototyping in the "Warm Precision" datasheet language.
Fixture-based testing patterns for Rust file operations (file_ops)
Reference for the original pick-theme bash script from dots. Load when implementing livery updaters to understand the existing behavior being migrated.
| name | commit |
| description | Create a git commit with livery conventions — conventional commits with fe/be scope prefix |
| argument-hint | ["optional commit message override"] |
Create a commit following livery conventions.
<type>(<scope>): <description> [#<github-issue>]
feat, fix, refactor, chore, docs, perf, ci
Determined by which files changed:
| Changed files | Scope | Example |
|---|---|---|
Only src/ | fe | feat(fe): add theme preview component #300 |
Only src-tauri/ | be | fix(be): handle tilde expansion in yaml paths #317 |
Both src/ and src-tauri/ | omit scope | feat: add lazygit updater #317 |
| Neither (docs, config, CI) | omit scope | docs: update AGENTS.md #324 |
Include the GitHub issue number (e.g., #317) if one is available in context — branch name,
conversation, or recent issue lookup.
Choose the right strategy based on what you're fixing:
| Situation | Strategy | Command |
|---|---|---|
| Fix belongs to the previous commit | Amend | git commit --amend --no-edit |
| Fix belongs to an older commit | Fixup + autosquash | See below |
| Change is a new distinct unit of work | New commit | Normal commit |
When a fix belongs to a commit that's not the most recent:
# 1. Find the target commit
git log --oneline -10
# 2. Create a fixup commit pointing to the target
git commit --fixup=<sha>
# 3. Autosquash to merge the fixup into the target commit
git rebase -i --autosquash <sha>~1
This keeps the branch history clean — each commit is a coherent, working change.
git status and git diff --staged to understand what's being committedgit add -A)