Loading...
Loading...
Found 3,747 Skills
Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.
Seismic platform help — Enablement Cloud, content management, Learning & Coaching, Aura AI, Digital Sales Rooms, Meeting Intelligence, LiveSend, LiveDocs, Programs, Seismic Exchange, API & integrations. Use when asking 'how do I do X in Seismic', configuring Seismic content library, setting up Learning paths, building Digital Sales Rooms, using LiveSend tracking, generating LiveDocs, managing enablement programs, using Aura AI, or integrating Seismic with CRM. Do NOT use for general sales content strategy (use /sales-content), sales coaching frameworks (use /sales-coaching), cross-platform deal room strategy (use /sales-deal-room), or connecting tools via Zapier (use /sales-integration).
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.
This skill should be used when the user asks to "create a pull request", "create PR", "open PR", "update a pull request", "update PR", "create an issue", "file an issue", "create a GitHub issue", "create a Claude Code issue", "report a bug in Claude Code", "create a Codex issue", "report a bug in Codex CLI", "create a Sablier issue", "file an issue in sablier-labs", "create a discussion", "start a GitHub discussion", "yeet a PR", "yeet an issue", "yeet a discussion", or mentions GitHub contribution workflows.
Capture Fusion skill workflow failure context and guide a draft-first bug reporting flow with explicit confirmation before any GitHub mutation.
Publish, discover, and buy digital artifacts on publish.new with x402 micropayments
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.
Guidance for Worktrunk, a CLI tool for managing git worktrees. Covers configuration (user config at ~/.config/worktrunk/config.toml and project hooks at .config/wt.toml), usage, and troubleshooting. Use for "setting up commit message generation", "configuring hooks", "automating tasks", or general worktrunk questions.
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.