Loading...
Loading...
Found 8,855 Skills
Create Git commits with Conventional Commits analysis, safe staging, and concise message generation. Use when the user asks to commit changes or create a git commit.
Use when pulling/syncing/updating/absorbing changes from a branch's parent (typically main) into the current branch, or cascading parent changes through a stack of dependent branches. Triggers on "pull from main", "merge main in", "update from parent", "sync from base", "catch up to main", "absorb parent changes", "rebase onto main" (intent only — implementation uses merge), "update the stack", "/inherit", or "my branch is behind". Pairs with /isolate (forks from parent) and /ship (pushes to target).
Adapt interfaces for different devices, breakpoints, platforms, and usage contexts without sacrificing core usability.
Information Question Generator. Given an article, paper, or book, extract its core viewpoints into Q-A pairs — Questions get straight to the point, no textbook-style phrasing; Answers are concise and clear, with formalized conclusions and complete logical chains. As readers follow the Q chain, each Answer drives home a key point, reproducing the author's entire reasoning process. Activate when the user says '问答', 'Q&A', 'QA', '提问', '抽取问题', '/ljg-qa', or shares an article, paper, or book and requests Q-A extraction. This tool triggers when the user wants ideas extracted not as a summary but as a sequence of incisive questions paired with answers. NOT FOR FAQ generation, glossary creation, or comprehension quizzes — this is intellectual scaffolding, not a study aid.
[Hyper] Diagnose and fix build failures, CI pipeline errors, and deployment errors across the entire repository or a specific folder. Routes simple build breaks directly; tracks complex multi-system failures via .hypercore/deploy-fix/ JSON flow.
Run Blacksmith Testbox for CI-parity checks, secrets, hosted services, migrations, or builds local cannot reproduce.
Operate on @spec facts — implement them in code, then tag @implemented. Use when asked to implement facts, implement the spec, build from the fact sheet, make facts true, or work through unimplemented requirements.
Send WhatsApp messages to users. After completing tasks, ask what they want next via WhatsApp and continue the conversation until they say they're done.
Watch a pull request or review cycle until it is ready to merge. Use when asked to babysit, monitor, or keep checking PR comments, reviews, and CI until all actionable issues are resolved.
Dispatch implementation tasks to agent teammates in git worktrees. Triggers: 'delegate', 'dispatch tasks', 'assign work', or /delegate. Spawns teammates, creates worktrees, monitors progress. Supports --fixes flag. Do NOT use for single-file changes or polish-track refactors.
Regenerate an existing printed CLI from scratch under the current Printing Press, with prior research and prior novel features carried into the novel-features subagent's reprint reconciliation rather than dropped on the floor. Pulls the CLI from the public library if it isn't local, recommends reuse-vs-redo of prior research based on age, then hands off to /printing-press with the right context. Use when a machine upgrade would benefit a published CLI more than manual polish. Trigger phrases: "reprint <api>", "regenerate <api>", "redo the <api> CLI", "rebuild <api> from scratch", "this CLI would benefit from a reprint".
Full-Process Web Novel/Story World Builder, suitable for users' overall novel writing needs such as saying "I want to write a novel", "Write a web novel", "Create a novel from scratch", "Help me write a novel of XX genre", "I want to write a novel", "Give me the entire novel creation process", "Auto-write a novel", "One-stop novel creation service", "Help me finish a novel", "How to write a novel with only an idea", etc. It automatically coordinates the full process of topic selection, outline design, writing, review, and polishing. Even if you only have a rough idea, it can help you complete a full work from 0 to 1 and build a unified story world. **All chapter-level operations are processed in parallel by sub-Agents, with each Agent responsible for a maximum of 3 chapters**