commit
starsforks
How to install commit?
kklimuk/docx-cli/commit
$npx -y skills add kklimuk/docx-cli --skill commitCreate well-structured git commits from the current working tree. Use when the user says 'commit', 'save my work', 'let's commit this', 'make a commit', or any variation of wanting to commit code to git.
SKILL.md
| 1 | # Commit |
| 2 | |
| 3 | Create clean, well-structured git commits that tell a coherent story. |
| 4 | |
| 5 | ## Process |
| 6 | |
| 7 | ### 1. Assess the Working Tree |
| 8 | |
| 9 | Run `git status` (never `-uall`) and `git diff` to understand what changed. Also run `git log --oneline -5` to match the repo's existing commit message style. |
| 10 | |
| 11 | If there are no changes, say so and stop. |
| 12 | |
| 13 | ### 2. Group Changes by Intent |
| 14 | |
| 15 | Look at the changed files and mentally group them: |
| 16 | |
| 17 | - **Feature**: new functionality (client + server + tests for the same feature = one commit) |
| 18 | - **Fix**: bug fixes |
| 19 | - **Refactor**: structural changes that don't change behavior |
| 20 | - **Docs**: documentation-only changes (CLAUDE.md, README, comments) |
| 21 | - **Test**: test-only additions or changes |
| 22 | - **Chore**: config, dependencies, tooling |
| 23 | |
| 24 | Rules for grouping: |
| 25 | - **Prefer fewer commits.** A feature that touches 15 files is still one commit if it's one logical change. |
| 26 | - **Only split when intent is genuinely different.** "Add collaborative editing" is one commit even if it touches client, server, DB, and tests. But "add collaborative editing" + "fix unrelated CSS bug" should be two commits. |
| 27 | - **For a first commit or large initial build, one commit is fine.** Don't artificially split an initial implementation. |
| 28 | - **Docs updates that accompany code changes go in the same commit.** Only separate docs commits for docs-only changes. |
| 29 | |
| 30 | ### 3. Present the Plan |
| 31 | |
| 32 | Before committing, show the user: |
| 33 | - How many commits you plan to make |
| 34 | - For each commit: the message and which files are included |
| 35 | - Ask for confirmation |
| 36 | |
| 37 | ### 4. Create the Commits |
| 38 | |
| 39 | For each commit: |
| 40 | 1. Stage the specific files with `git add <file1> <file2> ...` (never `git add -A` or `git add .`) |
| 41 | 2. Commit with a message using this format: |
| 42 | |
| 43 | ``` |
| 44 | <type>: <concise description> |
| 45 | |
| 46 | <optional body — explain WHY, not WHAT. The diff shows what.> |
| 47 | |
| 48 | Co-Authored-By: Claude <noreply@anthropic.com> |
| 49 | ``` |
| 50 | |
| 51 | Types: `feat`, `fix`, `refactor`, `docs`, `test`, `chore` |
| 52 | |
| 53 | Message guidelines: |
| 54 | - Subject line under 72 characters |
| 55 | - Use imperative mood ("add", not "added" or "adds") |
| 56 | - The subject should complete the sentence "This commit will..." |
| 57 | - Body is optional — use it for non-obvious context (e.g., "the old approach caused X" or "this unblocks Y") |
| 58 | - Always include the Co-Authored-By trailer |
| 59 | |
| 60 | ### 5. Verify |
| 61 | |
| 62 | After all commits, run `git log --oneline -10` to show the result. |
| 63 | |
| 64 | ## Safety Rules |
| 65 | |
| 66 | - **Never commit `.env`, credentials, or secrets.** Check staged files for these patterns and warn. |
| 67 | - **Never use `git add -A` or `git add .`** — always stage specific files. |
| 68 | - **Never amend a commit** unless the user explicitly asks. |
| 69 | - **Never force push.** |
| 70 | - **Never skip hooks** (`--no-verify`). |
| 71 | - **If a pre-commit hook fails**, fix the issue and create a NEW commit (don't amend). To diagnose, read the pre-commit hook (`.husky/pre-commit` or `.pre-commit-config.yaml`) to see what it runs, then run each command individually to find the failure. |
| 72 | |
| 73 | ## What NOT To Do |
| 74 | |
| 75 | - Don't write commit messages that describe every file changed. The diff does that. |
| 76 | - Don't split a single feature across 5 commits just because it touches 5 directories. |
| 77 | - Don't use vague messages like "update code" or "fix stuff". |
| 78 | - Don't commit generated files (`db/schema.ts`, `dist/`, `node_modules/`, `__pycache__/`). |
People who liked this also viewed
6 picksType
- grill-with-docsA relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.SkillsJul 2026
- lark-minutes飞书妙记：搜索妙记、查看妙记基础信息、下载/上传音视频、读取或编辑妙记的产物内容、改标题、替换说话人/关键词、申请妙记查看/编辑权限。当给出minute_token、本地音视频文件，要查/改/转妙记产物，或用户明确要主动申请妙记权限时使用；本地音视频转纪要/逐字稿优先走本 skill，不要用 ffmpeg/whisper 本地转写。不负责：获取会议关联妙记，或仅按自然语言标题定位纪要SkillsJul 2026
- lark-markdown飞书 Markdown：查看、创建、上传、编辑和比较 Markdown 文件。当用户需要创建或编辑 Markdown 文件、读取、修改、局部 patch 或比较差异时使用。不负责将 Markdown 导入为飞书在线文档，也不负责文件搜索、权限、评论、移动、删除等云空间管理操作。SkillsJul 2026
- docxUse this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files) or Word templates (.dotx files). Triggers include: any mention of 'Word doc', 'word document', SkillsJul 2026
- edit-articleSkills for Real Engineers. Straight from my .agents directory.SkillsJul 2026
- lark-note飞书会议纪要（Note）直查：已知 note_id 时查询纪要详情、展示类型、关联文档 token，并读取 unified 原始逐字记录。当用户已持有 note_id，或从文档显式 vc-node-id 获得 note_id 时使用。不负责会议/日程/妙记定位、文档标题搜索或 Docx 正文读取。SkillsJul 2026
