Loading...
Loading...
Found 126 Skills
Generate clear, conventional commit messages from git diffs. Use when writing commit messages, reviewing staged changes, or preparing commits.
Drafts and validates Git commit messages that follow the Conventional Commits specification and use Chinese as the primary commit language. Use when writing, reviewing, or fixing commit messages; choosing types or scopes; marking breaking changes; adding bodies or issue footers.
Commit Message Formatter - Auto-activating skill for DevOps Basics. Triggers on: commit message formatter, commit message formatter Part of the DevOps Basics skill category.
Guide for using git according to my preferences. Use it when you're asked to commit something.
Generate client-friendly monthly invoice summaries by analyzing Git commits and time sheet notes. Synthesizes technical work into business-focused bullet points suitable for client invoicing. Use when preparing monthly billing or project status reports. Triggers on "invoice summary", "monthly billing", "summarize work for client".
Create a git commit with clear, conventional commit messages. You MUST read this when the user wants to commit staged changes, write a commit message, or finalize code changes with proper conventional commit format since it describes how to follow the user's specific requirements.
Opt-in approval-first, whole-working-tree wrapper for the commit skill. Defaults to grouping all changes and requires the commit skill; selected installs must also install commit. Activate only when the user explicitly invokes `$commit-confirm` or explicitly asks to use the named commit-confirm skill. Do not activate merely because the user asks to review or propose commits, ask before committing, or wait for "go".
Use when creating git commits, writing commit messages, or following version control workflows
Use when the user asks to commit changes, organize commits, write commit messages, or split working-tree changes into Conventional Commits. Trigger on phrases like "commit my changes", "커밋해줘", "커밋 분리", "make commits", "/conventional-commit", or whenever the user wants to turn current changes into Conventional Commit-style commits. For commit + push use `conventional-commit-push`; for rewriting non-Conventional commit history use `conventional-commit-rewrite`.
Tạo branch riêng cho mỗi opsx change (không code thẳng trên main), tự động commit sau khi user xác nhận UI ổn (qua ui-checkpoint), merge vào main khi change đã archive xong, và xử lý yêu cầu "quay lại", "undo", "bỏ tính năng vừa thêm" bằng git thay vì đọc lại code để xóa thủ công - tiết kiệm token đáng kể. Dùng skill này ngay khi 1 change mới được tạo (để branch), sau ui-checkpoint (để commit), sau archive (để merge), hoặc bất cứ khi nào user muốn hủy/quay lại thay đổi gần đây.
Review code changes against a plan using the plan location and implementing git commit(s).
Automatically generate and submit ECP time reports from the day's Git commits on the release branch. Applicable to scenarios such as "auto-fill daily time reports", "backfill time reports based on commit descriptions", and "scheduled automatic writing of ECP time reports".