.fyi
SkillsMCPPluginsSubagents

Browse by category

DevOps & CI/CD SkillsProductivity & Workflow SkillsOther SkillsProduct & Project Management SkillsDocumentation & Knowledge SkillsCode Review & Refactor SkillsBackend & APIs SkillsAgent Meta & Communication SkillsResearch SkillsSecurity SkillsUX UI & Design SkillsTesting & QA SkillsSee all →

Every Claude Code skill, MCP server, plugin and subagent in one directory. Searchable, comparable, and one command from installed. Live stats from GitHub, npm and PyPI.

We're on Product HuntYour agent's app storeCheck it out →
Agent SkillsMCP ServersPluginsSubagentsCoding Agents
CollectionsOfficial publishersGlossaryFAQBlogSearchSavedFeedback
PrivacyTermsllms.txtSitemap

made with ♥ · © 2026 aaaa.fyi

Independent project · real data from public registries

…/motlin/claude-code-plugins
home/skills/motlin/claude-code-plugins
motlin avatar

motlin/claude-code-plugins

43 skills

View on GitHub
$npx skills add motlin/claude-code-plugins
SkillInstalls
build-dev-serverStart or restart a project dev server on a specific or discovered port, wait until it is ready, and monitor it for automatic recovery.—build-fixCommit changes, run git-test precommit checks, and fix failures. Use when asked to fix build, test, lint, typecheck, or precommit failures.—build-test-allRun tests across all commits and loop on failures until all pass. Use when asked to run or fix test-all for a branch.—build-test-branchTest every commit in the current branch, fix failures, create fixup commits, and repeat until all commits pass.—build-test-setupConfigure git-test for the current repository. Use when git test is missing or the user asks to set up branch testing.—cliCLI guidelines. Use whenever using the Bash tool, which is almost always. Also use when you see "command not found: __zoxide_z" errors.—code-generationThis skill should be used when the user asks to "fix formatter-off", "fix code generation formatting", "fix auto-formatted string concatenation", "add…—code-qualityCode quality guidelines. ALWAYS use skill for ANY code changes.—comment-cleanupKeep code comments concise and durable, or clean redundant comments without changing code behavior.—create-pull-requestCreate a GitHub pull request the user's preferred way. Use whenever opening, creating, or raising a PR with gh.—git-clean-worktreesRemove git worktrees safely without force.—git-commitCommit local changes with careful staging and single-line messages. Use for all git commit operations.—git-commit-chunksSplit local changes into multiple logical commits. Use when the user asks to commit changes in chunks.—git-conflictsResolve git merge or rebase conflicts and continue the operation.—git-rebaseRebase local commits on the configured upstream using the plugin rebase script.—git-rebase-allRebase all local branches onto the configured upstream branch.—git-reword-commitsRewrite in-scope commit messages to single-line git-workflow messages with git history reword.—git-split-branchSplit the current branch into multiple branches with one commit each.—git-workflowCommit message format and git workflow rules. ALWAYS use this skill for every git commit — no exceptions — and whenever rewording an existing commit message.—git-worktreeCreate a git worktree in a peer directory using the plugin worktree script.—github-actions-fixDebug and fix failing GitHub Actions checks for the current commit. Use when asked to fix CI, GHA, or GitHub Actions failures.—investigation-reportProduce a single self-contained HTML report that explains a command-line investigation — the commands actually run, their real output, and just enough…—justfile-styleStyle guidelines for justfile recipe documentation. Use when writing or editing justfiles to ensure consistent and concise documentation.—liquibase-lock-resolverDiagnose Liquibase change-log lock failures in Maven tests and remove only stale H2 database files from build output directories before rerunning the affected…—markdown-add-taskAdd a self-contained task to .llm/todo.md. Use when the user asks to add one task or append work to the markdown task list.—markdown-do-all-tasksWork through all incomplete tasks in .llm/todo.md with one subagent and commit per task, continuing past blocked tasks.—markdown-do-one-taskFind and implement the next incomplete task from .llm/todo.md.—markdown-import-planImport a plan markdown file into .llm/todo.md as self-contained implementation tasks.—markdown-plan-tasksConvert a planning discussion into self-contained tasks in .llm/todo.md.—markdown-sweep-todosFind TODO comments in the codebase and add them to .llm/todo.md as tasks.—maven-cliMaven CLI invocation patterns. Use whenever running `mvn` commands in Java/Maven projects.—openrewriteOpenRewrite recipe test maintenance. Use when fixing test failures, import ordering issues, type validation problems, IDE warnings, or writing comprehensive…—openrewrite-analyze-recipesDry-run configured OpenRewrite recipes, count and rank violations, and optionally run one selected recipe without committing.—openrewrite-recipesOpenRewrite recipe authoring patterns and API best practices. Use when writing or editing OpenRewrite recipe Java source code (visitors, matchers, type checks,…—openrewrite-violationsApply every configured OpenRewrite recipe with violations on a dedicated branch, creating one commit per named leaf recipe and verifying the cumulative result.—pom-orderingEnforce Maven POM dependency ordering rules. This skill should be used when editing pom.xml files.—precommitRunning precommit checks and build validation. ALWAYS use after ANY code changes.—tasksWork with markdown-based task lists in .llm/todo.md files. Use when managing tasks, working with todo lists, extracting incomplete tasks, marking tasks…—team-leadCoordination guidelines for leading a team of task-executing agents—team-memberWorkflow guidelines for team members executing tasks—test-assertionsWrite test assertions as complete, strict deep-equality checks, and hold existing tests to the same standard.—test-dataThis skill should be used when writing, reviewing, or modifying test code that contains literal values like timestamps, names, IDs, paths, or URLs.—wipRun on /wip or for a whole-repository cleanup spanning multiple worktrees and branches.—