Loading...
Loading...
Found 3,748 Skills
Agent-powered GitHub PR reviews with smart semantic triage. Categorizes changes as MECHANICAL (skip), NEW LOGIC (read), or BEHAVIORAL (verify) — so agents never waste tokens reading lock files or formatting diffs. Includes remote file reading, text/AST search across PR or full repo, and comment posting. No local clone needed. Use when asked to review a PR, check a pull request, look at PR changes, or given a PR number/URL to review.
Discovers relevant Fusion skills through Fusion MCP first, falls back to GitHub-backed catalog inspection when needed, returns concise matches with purpose and next-step guidance, and handles install, update, or remove intent without guesswork. USE FOR: finding a skill for a task, asking what to install, checking update or remove guidance, discovering available Fusion skills. DO NOT USE FOR: creating new skills, performing the task itself, or inventing results when discovery signals are unavailable.
Publish, discover, and buy digital artifacts on publish.new with x402 micropayments
Sync all updated skills in ~/.claude/skills/ljg-* to the GitHub repo (ljg-skills). First push to the master branch (in org-mode output style), then switch to the md branch, perform basic markdown conversion, and push. Use when the user says '/ljg-push', 'push skills', 'sync skills', 'sync ljg', or whenever ljg-* skills are updated and need to be shipped. DO NOT use this for pushing non-ljg skills or arbitrary Git repos.
Design multi-stage CI/CD pipelines with approval gates, security checks, and deployment orchestration. Use when architecting deployment workflows, setting up continuous delivery, or implementing GitOps practices.
Use when a user asks to debug or fix failing GitHub PR checks that run in GitHub Actions; use `gh` to inspect checks and logs, summarize failure context, draft a fix plan, and implement only after explicit approval. Treat external providers (for example Buildkite) as out of scope and report only the details URL.
Design and implement CI/CD pipelines with GitHub Actions, GitLab CI, Jenkins, or CircleCI. Use for automated testing, building, and deployment workflows.
Capture Fusion skill workflow failure context and guide a draft-first bug reporting flow with explicit confirmation before any GitHub mutation.
This skill should be used when the user says "setup", "deploy to railway", "initialize", "create project", "create service", or wants to deploy from GitHub. Handles initial setup AND adding services to existing projects. For databases, use the database skill instead.
Install Claude skills from GitHub repositories with automated security scanning. Triggers when users want to install skills from a GitHub URL, need to browse available skills in a repository, or want to safely add new skills to their Claude environment.
Install a rich Claude Code statusline into ~/.claude/hooks/ and ~/.claude/settings.json. Displays model, git context, token usage, effort level, 5h/7d usage limits, and active /loop count with next-fire time.
Git commit with enforced quality gates, proper message format, and safe push workflow