Loading...
Loading...
Found 2,779 Skills
Use when the user needs to run GitNexus CLI commands like analyze/index a repo, check status, clean the index, generate a wiki, or list indexed repos. Examples: "Index this repo", "Reanalyze the codebase", "Generate a wiki"
Check, create, and manage Git worktrees for parallel branch development. Suitable for scenarios such as batch-creating worktrees based on local branch patterns, placing worktrees in directories at the same level as the repository, avoiding duplicate worktree creation for branches already checked out in other directories, verifying branch-to-worktree path mappings, or preparing isolated workspaces before making modifications across multiple branches.
Safety guardrails for destructive commands. Warns before rm -rf, DROP TABLE, force-push, git reset --hard, kubectl delete, and similar destructive operations. User can override each warning. Use when touching prod, debugging live systems, or working in a shared environment. Use when asked to "be careful", "safety mode", "prod mode", or "careful mode".
Chinese functional specification creation tool used to convert natural language feature descriptions into structured functional specification documents. Supports automatic branch name generation, Git branch creation, specification file initialization, and quality verification. Trigger words include: "speckit specification", "functional specification", "create specification", "feature description conversion", "speckit-specify". Use this skill when users need to convert feature ideas into structured specifications.
Create versioned releases with consolidated changelogs. Gathers shipped items, generates CHANGELOG.md entry, creates git tag, and GitHub Release. Use after multiple /ship tasks are merged.
Initialize GitHub Project Management config. Auto-discovers project schema (fields, views, repos) and generates .ghpm/config.json + .ghpm/cache.json.
GitHub PR review threads—KEEP/DISCARD triage, replies, KEEP-only code changes, lint/test/push. Open PRs only; not for creating PRs (create-pr-jp).
Workflow for handling a Linear issue end-to-end. Uupdate Linear, create a git worktree from dev, implement the change, verify it, and open a GitHub PR linked to the issue.
Integration patterns for the GitHub Accessibility Scanner Action (github/accessibility-scanner). Teaches agents how to detect scanner presence, parse scanner-created issues, correlate findings with local scans, and track Copilot-assigned fix status.
Add one or more Git repositories to Cyrus configuration so it can process issues from those repos.
Automatically create a PR to register insights, conventions, and best practices obtained from the current project as rules in the TBSten/skills repository. It runs the entire end-to-end process: collecting insights from the project's CLAUDE.md, .claude/rules/ directory and codebase, packaging them as reusable Claude Code rules, and creating the PR. Rules are files stored in .claude/rules/, and unlike skills, they do not require frontmatter. RULE.md serves as the main rule body, while detailed documentation (<rule-name>.md / <rule-name>.ja.md) is placed directly under the rules/ directory. Use when the user requests: "Register insights as rules", "contribute rule", "Share this rule", "Register as a rule", "Compile rules into a PR", "Turn this convention into a rule", "Turn best practices into rules". gh CLI and git must be installed.
Fetch a GitHub pull request body and its messages for the current repository.