Loading...
Loading...
Found 2,779 Skills
Perform code optimization for .vue, .js, .css, .scss, .less files in Vue2 projects. By default, optimize git changed files, or execute according to the user-specified scope. Unify code structure, BEM styles, semantic naming and key comments to improve readability and collaboration efficiency. Do not generate new components or modify business logic. Trigger scenarios: Users request code optimization, code structure standardization, unified naming, Vue2 component optimization, and code style organization.
Analyze git diffs for risk scoring, reviewer recommendations, and change classification
Create new skills for the lovstudio ecosystem. Each skill is its own independent GitHub repo at lovstudio/{name}-skill, scaffolded locally at ~/lovstudio/coding/skills/{name}-skill/, symlinked to ~/.claude/skills/ for immediate use, and registered in the central index at ~/lovstudio/coding/skills/index/ (skills.yaml + README.md). Lovstudio conventions: `lovstudio:{name}` frontmatter, mandatory README.md per skill, AskUserQuestion interactive flow, standalone Python CLI scripts with argparse, CJK text handling. Use when the user wants to create a new skill, add a skill to the lovstudio ecosystem, scaffold a skill, or mentions "新建skill", "创建skill", "封装成skill", "new skill", "add skill", "scaffold skill", "生成skill".
Analyze staged Git changes and generate a concise Chinese commit message that follows repository commit style. Use when the user asks to commit code, generate a commit message, or summarize staged changes into a Chinese Git commit title and bullets.
[Hyper] Create, enter, list, remove, clean up, or repair Git worktrees for isolated branches and parallel agent sessions, including direct `git-worktree <ARGUMENT>` creation without follow-up questions. Use when the user asks for git worktree setup/removal, branch-per-folder workflows, parallel Codex/Claude/Cursor workspaces, or the repository-local `.hypercore/git-worktree/<folder_name>` convention; when creating and no argument/task is clear, ask what work will happen there in the user's language, derive the folder name, then move subsequent work into the new worktree.
Use Crabbox for OpenClaw remote Linux validation, warmed reusable boxes, GitHub Actions hydration, sync timing, logs, results, caches, and lease cleanup.
Advanced git workflows with branch management, conflict resolution, and PR lifecycle
Open Orbit briefing skill — selected by the Orbit pipeline when GitHub is the user's only connected connector, or when the user explicitly scopes their daily digest to GitHub. Pulls the past 24 hours of PRs, review requests, issues, CI runs, and merges from the user's authenticated GitHub connection and renders them in a layout that mirrors GitHub's native Notifications + PR-diff visual language. This skill should not be triggered manually — it is invoked by Orbit's daily-digest scheduler against live GitHub data.
GitOps continuous delivery toolkit for Kubernetes with Flux CD. Use for declarative deployments, Helm chart automation, Kustomize overlays, image update automation, multi-tenancy, and Git-based continuous delivery.
Break a large GitHub issue into independent, mergeable sub-issues with clear scope and acceptance criteria. Use when user says 'split this issue', 'break this down', 'this issue is too big', 'splice this epic', 'create sub-issues', or 'decompose this task'. Do NOT use for planning implementation steps within a single issue (use plan-issue) or for creating a fresh issue from scratch.
Generate exactly one high-quality Conventional Commit message from the current Git diff. Use when Codex needs to inspect staged changes, summarize the dominant intent, and return only the final commit message with no analysis or extra text.
Read a GitHub Issue, create a detailed plan in `_/local-plans/<issue-number>-<slug>.md`, and implement the code **after user approval**. After implementation, perform a security review (OWASP Top 10) → run tests → commit using Conventional Commits. Used for implementation requests where an Issue number or URL is provided, such as "Implement Issue #N" or "Start working on this Issue".