Loading...
Loading...
Found 2,779 Skills
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".
Standard end-to-end workflow for shipping a feature/bugfix from a Jira task to a merged GitLab MR. Use when the user references a Jira task ID (WRA-XX, etc.), asks to "start a task", "create branch from task", "review the last change", "review the whole branch", "commit and push", "create a merge request", "review the MR !N", "post review result to the MR", "fix all issues", or "merge the request". Covers branch naming, commit format, MR creation, micro + macro code review (3-agent parallel), fix loop, and merge.
Use GitHits CLI for canonical open-source examples, indexed source, docs, grep, file listing, and code navigation. Activate when verifying library behavior from source or examples. For metadata, vulnerabilities, dependency graphs, or changelogs, use githits-package instead.
Generate a single-file interactive HTML code-review artifact for a GitHub PR. Fetches the diff via the gh CLI, performs an honest severity-coded self-review, and renders an artifact with: collapsible per-file diffs with colored inline annotations, severity filter chips, per-finding checkboxes, and a "Create feedback prompt" modal that aggregates the checked items into a paste-ready follow-up prompt ending with "Please address this feedback. Address each individual item in its own conventional commit." Use this skill whenever the user wants to review a pull request visually, asks for an HTML or static review artifact, says "review PR", "review this PR", "build a PR review", wants color-coded findings, feedback aggregation, or a review file they can share — even if they don't explicitly say "HTML". Also trigger on "code review artifact", "interactive review", "feedback prompt for a PR", or when the user mentions reviewing a specific PR number.
Application-developer GitOps work for OpenChoreo — onboarding Components (BYO image or source-build), authoring Workloads and `workload.yaml` descriptors, attaching PE-authored Traits, wiring component dependencies, generating ComponentReleases and ReleaseBindings via `occ` file-mode, promoting releases across Environments (single, project-wide, bulk), applying per-environment overrides, opening PRs upstream, and verifying Flux reconciliation. Use when the user says 'add a component to the GitOps repo', 'release my service via Git', 'open a PR for this Workload change', 'promote to staging via Git', 'bulk-promote my project', 'roll back a release', or operates a developer-side change from inside a scaffolded GitOps repo.
Hypothesis-driven debugging with ranked hypotheses, git bisect strategy, instrumentation planning, and minimal reproduction design. Triggers on: "debug this systematically", "root cause analysis", "bisect this bug", "rank hypotheses", "isolate this issue", "minimal reproduction". NOT for general reasoning.
Generate and publish blog posts from any project to kelegele/agent-blog. ZERO DEPENDENCIES — does NOT require Node.js, pnpm, git, or any local build tools. Works with only a browser and a GitHub token. Triggers on: "写篇博客", "blog this", "发博文", "publish blog", "把项目写成文章", "写篇文章", "blog it", "post article", "新文章", "new blog post", "blog this project", "发一篇博文", "写一篇博文", "blog post about this", "edit blog post", "修改文章", "更新博文", "edit article". Collects project context, collaborates on outline, writes Markdown with correct frontmatter, validates article format, generates a standalone HTML preview by reading live blog source, manages draft/review/publish flow. Pushes to kelegele/agent-blog main branch. Vercel auto-deploys on push. Use this skill whenever the user expresses intent to write about their current work as a blog post.
Build and maintain the Hermes Atlas ecosystem map with quality filtering, RAG chatbot, and live GitHub star tracking
Emulate supported AI code-review GitHub Actions locally and print a terminal-only review from portable skill instructions. Use when running /review-action or checking local PR-review feedback before publishing.
Performs a comprehensive security review of code changes in a GitHub PR or issue. Checks out the branch, analyzes changed files against a 9-category security checklist, and produces PASS/WARNING/FAIL verdicts. Use when reviewing pull requests for security vulnerabilities, hardcoded secrets, injection flaws, auth bypasses, or insecure configurations. Trigger keywords - security review, code review, appsec, vulnerability assessment, security audit, review PR security.
Run a read-only, fresh-context branch-diff code review and report findings. Use when running /review-code, before finishing issue work, or when a local review gate should inspect committed, staged, unstaged, and untracked changes without mutating code or GitHub state.