Loading...
Loading...
Found 126 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.
Standardized git commits following Conventional Commits. Supports mapping to GitHub and GitLab.
Creates Checkmk werks (changelog entries) from git commits
Validate-then-fix workflow for PR review comments: Fetch, Validate, Plan, Fix, Commit. Use when user wants to address PR feedback, fix review comments, or resolve reviewer requests. Use for "fix PR comments", "address review", "pr-fix", or "resolve feedback". Do NOT use for creating PRs, reviewing code without fixing, or general debugging unrelated to PR comments.
Handles commit flows by detecting changes, optionally running validator validation, and completing commits for requests such as "commit with validator", "run checks before commit", "run validator then commit", or "skip validator and commit".
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.
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.
Generate semantic commit messages following conventional commits format. Use when committing code, staging changes, writing commit messages, requesting git commit, or when user mentions commit, commit message, conventional commits, semantic commits, git commit, stage changes, create commit. Supports monorepo package version tracking.
[Implementation] ⚡⚡ Implement a feature automatically ("trust me bro")
Creates commits with conventional format and validation. Use when committing changes or generating commit messages.
Full feature pipeline — pre-flight checks, TDD cycle, scope guard, quality commit. Combines pre-flight + tdd + scope-check + quality-commit into one flow. Use when implementing a feature, adding an endpoint, or building any non-trivial code change.