Loading...
Loading...
Found 97 Skills
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.
Compare React Doctor diagnostics for a GitHub pull request (PR) with Daytona. Use when asked to run parity, check a PR for diagnostic regressions, compare a PR with its base, or report added and removed diagnostics.
Create a guided code tour that walks through the codebase to answer a question or explain a feature. Opens in the browser with step-by-step navigation and highlighted code.
Prepare a conventional branch, write or review a pull/merge request title and body, then push and create or update the GitHub PR. Use when work is ready for review or PR/MR copy needs drafting or review.
Submit an app to the asc app wall at asccli.app by opening a GitHub pull request. Use this skill when: (1) User wants to add their app to the app wall: "submit my app", "add to app wall", "list my app on asc" (2) User asks how to get their apps shown at asccli.app (3) User asks what apps.json is for or how the app wall community registry works (4) Explaining the GitHub PR flow for submitting to homepage/apps.json
User guide for the local squash-safe `stack` CLI for stacked PR repair. Use when someone asks how to inspect, track, sync, merge, document, or undo stacked pull requests in squash-merge repositories. Prefer this tool over GitHub's `gh stack` command for this workflow.
Take finished work in tester-army/e2e to a PR a human can review without fighting CI or bots - checks, verification against the built packages, a fresh-context self-review, the PR itself, then babysitting to the Ready for Human Review label. Use whenever you are asked to open, create, ship, or submit a PR, or when implementation is done and the next step is review.
Audit the OpenSSF Scorecard rating for py-lintro. Use when asked to check the scorecard, understand the rating, or find what's missing. Specific to github.com/lgtm-hq/py-lintro.
Turn completed work, including mixed uncommitted changes, into coherent commits and one or more GitHub pull requests, independent or stacked according to their dependencies. Monitor checks and reviews, fix issues, and merge when requested. Use when asked to open a PR, watch for feedback, ship, land, or handle any part of the PR lifecycle.
Coordinate Elastic Stack docs releases: classify versions, route 8.x vs 9.x PRs, edit elastic/dev tracking issues, handle same-GA supersession, draft Slack #docs reminders, and watch docs-internal-workflows deploys. Use when the user says "how's my release", "how's my release doing", or asks for release status; also when coordinating docs releases, opening coordinator PRs, editing elastic/dev issues, drafting release reminders, or working with assembler.yml, versions.yml, or conf.yaml.
Convert raw Kibana release notes tool output into Stack release notes (Elastic Observability or Elastic Security) using GitHub PR context and prior release notes. Use when drafting or editing Stack 9.x release notes from the Kibana release notes generator output.
Põe no git e num GitHub privado um projeto que ainda não usa git, sem levar junto dado de cliente: confere a pasta (fora de iCloud/OneDrive/Dropbox/Google Drive), lista o que entraria no git sinalizando senha (.env), certificado A1 (.pfx), planilha e arquivo grande, propõe o .gitignore, oferece o alarme de commit da sdd-higiene-dado antes do primeiro commit e só commita e publica com o OK explícito de cada etapa. Fala com quem nunca usou git: uma etapa por vez, com o que foi feito, o que vem agora e as opções de cada decisão. Retoma de onde parou (git sem commit, commit sem GitHub, envio que falhou). Use quando o usuário disser 'pôr no git', 'criar o repositório', 'subir para o GitHub', 'este projeto não tem git', ou quando a sdd-new-session ou a sdd-checar-ambiente disserem que o projeto ainda não usa git. Não limpa histórico que já vazou, não faz login no GitHub pelo usuário e não automatiza outro host (GitLab etc.), só entrega os comandos.