Loading...
Loading...
Found 157 Skills
Author and review GitHub Actions workflow YAML safely so syntactically-valid YAML can't ship a workflow that GitHub Actions refuses to run. USE FOR: editing, adding, or reviewing any file under .github/workflows/, writing run-name/name/if/env/run values that contain ${{ }} expressions, diagnosing a run that fails with 'This run likely failed because of a workflow file issue' and no jobs starting, deciding when a workflow scalar must be quoted, validating workflows with actionlint. DO NOT USE FOR: authoring application YAML unrelated to GitHub Actions, Azure Pipelines, GitLab CI, or non-workflow YAML. SCOPE: this skill covers *syntactic/structural* correctness of workflow YAML (quoting, parsing, actionlint); for *semantic and functional* workflow design (what a workflow should do, agentic-workflow behavior), see .github/agents/agentic-workflows.agent.md — the two are complementary. INVOKES: actionlint (downloaded pinned binary) plus git/grep for inspection.
Manage integrate Sentry with CI/CD pipelines. Use when setting up GitHub Actions, GitLab CI, or other CI systems with Sentry releases and source maps. Trigger with phrases like "sentry github actions", "sentry CI", "sentry pipeline", "automate sentry releases".
(NS) NextStage harness face — session boot, artifact layout, AND brownfield prepare. Use whenever the user says /ns-harness, prepare this repo, harness prepare, generate architecture rules, architecture-rules.md, write AGENTS.md, reverse-engineer the codebase, engenharia reversa, brownfield map, or bootstrap brownfield — even if they name ns-harness-prepare, ns-architecture-rules, ns-agent-generator, ns-codebase-reverse-spec, or ns-bootstrap-brownfield. Route to references/prepare.md (full chain) or the matching worker reference. Do NOT use for coding, SDD versions, or GitLab issue execution.
Run /code-review, /simplify, /brooks-review, /review, /ask-exemplar, and /zero-tech-debt on a change via parallel subagents, address the meaningful findings, fold the fixes into clean commits, and force-push with lease. Use when the user wants to review-and-fix a change before merge: uncommitted work, the current feature branch, or a GitHub PR / GitLab MR. Triggers include "review-fix", "review and fix this PR/MR", "polish this branch", or "run the reviews, address the suggestions, then force-push".
Find the pull request for the current branch on GitHub, GitLab, Bitbucket Cloud or Data Center, or Azure DevOps; retrieve unresolved inline CodeAnt AI review threads through the source-control provider; validate each finding; apply safe minimal fixes; verify them; and resolve only fixed threads. Use when asked to address, fix, triage, or resolve CodeAnt PR comments without installing or using codeant-cli.
Workflow Specifications Adapted to Domestic Git Platforms and Team Habits - Full Coverage of Gitee, Coding, Jihu GitLab
Reference for Domestic Git Platform Configuration - Differences in SSH/HTTPS/Credentials/CI Integration and Mirror Sync Configuration for Gitee, Coding.net, Jihu GitLab, and CNB. Only invoke when the user explicitly uses /chinese-git-workflow; do not trigger automatically based on context.
Bump the NVIDIA PyTorch base image (`nvcr.io/nvidia/pytorch:<YY.MM>-py3`) used by Megatron-LM CI. Covers the two pin sites (GitHub CI in `docker/.ngc_version.dev` and GitLab CI in `.gitlab/stages/01.build.yml`), the post-bump CI loop (re-run functional tests, refresh golden values, mark broken tests), and the gotchas that bit PRs
(NS) Gated PM workflow — clarify, structure, RICE/WSJF, sprint plan, PERT/Monte Carlo forecast; risk, status, meeting, OKR. Also commercial budget (orçamento, Function Points, proposta comercial; COSMIC/CFP only if asked), triple productivity delivery schedule (cronograma P100/P85/P50, prazo, when we deliver), and requirements enricher / grill-me for GitLab issues or chat. Use on transcripts, backlog, timeline, delivery date, status, orçamento, cotação, cronograma, enrich requirements — even if PM is unnamed. On "help" / "exemplos", list example prompts only. Do NOT use for coding, SDD requirements generation, or GitLab issue execution.
Use when the user wants to automate WeChat mini-program upload, preview, or npm packaging via CI/CD, generate deployment scripts, set up miniprogram-ci workflows, or create preview QR codes automatically. Trigger whenever the user mentions "上传小程序", "预览", "CI 部署", "miniprogram-ci", "自动化上传", "发布小程序版本", "生成预览二维码", "打包npm", "pack-npm", "构建npm依赖", "GitHub Actions 小程序", "pnpm 小程序部署", or asks to integrate WeChat mini-program with continuous integration pipelines (GitHub Actions, GitLab CI, etc.).
Create or update GitHub issues from screenshots, emails, messages, or any visual/text input. Extracts structured data, redacts PII, detects issue templates, proposes issues for approval, then files them via gh CLI. Don't use for GitLab/Jira tickets, opening pull requests, or fixing the bug described in the issue.
(NS) Ad-hoc coding worker — bug fixes, small refactors, scripts, migrations — without full SDD. Entry priority 5: use for "just implement this", "quick fix", or concrete coding without execution-handoff (also C2 under ns-code-autonomous). Do NOT use for GitLab ISSUE_URL (ns-execution-gitlab-issue), multi-day/version scope (ns-spec-driven), diagnosis-only (ns-code-investigator), or when execution-handoff.md exists. Do NOT generate requirements/tasks/handoff.