Loading...
Loading...
Found 7,951 Skills
Use when changing CFO Stack ledger conventions, process docs, Beancount metadata rules, or canonical ledger/file layout guidance that should stay out of AGENTS.md.
Manage the lifecycle of ExecPlans — self-contained, living specifications for multi-step work. Creates plans in the correct format, enforces living section updates, and handles the active → completed transition. Use for any work expected to take more than one session or touching more than 3 files. Triggers: "create a plan", "write a plan", "start plan", "continue plan", "resume plan", "finish plan", "complete plan", multi-step features, refactors, or tasks spanning sessions.
Execute Azure deployments for ALREADY-PREPARED applications that have existing .azure/deployment-plan.md and infrastructure files. DO NOT use this skill when the user asks to CREATE a new application — use azure-prepare instead. This skill runs azd up, azd deploy, terraform apply, and az deployment commands with built-in error recovery. Requires .azure/deployment-plan.md from azure-prepare and validated status from azure-validate. WHEN: "run azd up", "run azd deploy", "execute deployment", "push to production", "push to cloud", "go live", "ship it", "bicep deploy", "terraform apply", "publish to Azure", "launch on Azure". DO NOT USE WHEN: "create and deploy", "build and deploy", "create a new app", "set up infrastructure", "create and deploy to Azure using Terraform" — use azure-prepare for these.
Generates structured changelogs and release notes from git history and PR descriptions. Classifies changes into breaking, features, fixes, performance, and docs. Filters internal-only changes, detects breaking changes, and produces human-readable entries linked to source PRs. Triggers on: "generate changelog", "write release notes", "compose changelog", "what changed since", "changes since last release", "prepare release", "release notes for", "changelog for", "summarize changes", "diff since tag". Use this skill when preparing a release and needing to summarize changes for users.
Use when iterative review-fix cycles are needed on a plan or implementation — bounded loop with severity gating, automatic fixes, and finding disposition.
Adopt the Three Provinces and Six Ministries style code review, output structured review conclusions in five stages: Zhongshu Sheng, Shangshu Sheng, Six Ministries, Menxia Sheng, and Jinyiwei
Browse the XBTI Gallery — all community-created BTI personality tests at xbti.lovstudio.ai. Trigger when user says "XBTI Gallery", "xbti-gallery", "BTI列表", "浏览人格测试", "show BTI cases", or wants to see available BTI variants.
Use when deleting a Zeabur project. Use when user says "delete project", "remove project", or "clean up project". Use when tearing down test or temporary projects. Always confirm project name and ID with the user before deleting.
Use when pulling live GitHub state back into existing gh-infra manifests with `gh infra import --into`, especially for write/patch/skip decisions, shared file sources, template-backed files, and import safety rules.
Review code changes against STYLE_GUIDE.md before committing or creating PRs. Catches naming violations, import ordering issues, anti-pattern reintroduction, and convention drift. Run after /setup-ai or /generate-comprehensive-style-guide has created a style guide.
Reviews the feature you just built and adds missing test coverage. Focuses on behavior that matters — not coverage metrics. Use after completing a feature to identify untested code paths, edge cases, and risk areas.
Primary router skill for broad .NET work. Classify the repo by app model and cross-cutting concern first, then switch to the narrowest matching .NET skill instead of staying at a generic layer.