Loading...
Loading...
Found 305 Skills
Create factual working journal entries in Notes/WorkingJournal/ after completing analysis work. Use when user asks to "summarize work", "document results", or "create working journal entry". Ensures code is committed, copies figures to attachments, and creates objective summaries with citations.
This skill should be used when the user requests "commit", "git commit", "create commit", or wants to commit staged/unstaged changes following conventional commits format
Generate high-quality git commit messages following Conventional Commits and Chris Beams' Seven Rules. Infers WHY from context and provides clear guidance on structure, scope, and body content.
Creates Checkmk werks (changelog entries) from git commits
Create well-formatted commits with conventional commit messages and emoji
[Hyper] Commit and push in one action, including from linked Git worktrees. Use when the user asks to commit and push together, save and push changes, or run `/git-maker`; it performs safe commit grouping first, then automatically pushes without a second confirmation.
List recent git commits that are linked to agent sessions, optionally filtered by branch or repo. Use when the user asks "show agent commits", "what has the agent shipped", or wants a list of commits with their session context.
Generate a git commit message compliant with Conventional Commits 1.0.0 (and the de facto @commitlint/config-conventional rules) from currently staged changes. Outputs Korean by default, or another language if the user explicitly requests it. Trigger when the user asks for a commit message — e.g. "/conventional-commits", "write a commit message", or any equivalent. Scope is limited to producing the message text; executing `git commit` is outside this skill's responsibility.
Author's cleanup checklist before committing or submitting a PR. Use before any commit or PR to ensure code is clean, focused, and ready for review. Checks for debug code, secrets, redundant changes, and scope creep.
Generate appropriate commit messages and maintain git log documentation. Use when preparing to commit changes, reviewing git history, or maintaining project change documentation. Provides commit message generation, git log maintenance, and quick command reference.
Create git commits following repository style. Use when user asks to "create a commit", "commit changes", "/commit", or requests committing code to git.
This skill should be used when the user asks to "wrap up session", "end session", "session wrap", "/wrap", "document learnings", "what should I commit", or wants to analyze completed work before ending a coding session.