insights
Generate codebase activity summaries (daily/weekly/catchup/view) from Azure DevOps PRs, work items, local git, and optionally Confluence. Trigger when user says "/dev-azdo:insights", asks "what happened", "codebase activity", "team summary", or wants a PR/commit roll-up.
pr-comments
Manage Azure DevOps PR comments — post new code comments, read and assess existing threads. Trigger when user says "/dev-azdo:pr-comments", asks to add/post a comment on a PR, review PR feedback, or check PR comment status. Input is PR id/URL, or empty to use current branch's PR.
pr
Manage Azure DevOps pull requests — create, checkout, list, complete. Trigger when user says "/dev-azdo:pr <op>", "create PR", "checkout PR 123", "list PRs", "complete PR", or otherwise asks to operate on an AZDO pull request.
ticket-comments
Add, update, or delete a comment on an Azure DevOps work item (the Discussion thread) via the dedicated Comments REST API, with Markdown rendering. Trigger when the user says "comment on ticket #N", "add a comment to the work item", "update/edit the AzDO comment", "delete a work-item comment", or asks to post discussion notes on a ticket. Use INSTEAD OF patching `System.History` whenever the comment should render as Markdown or may need to be edited or deleted later.
ticket-create
Create an Azure DevOps work item (Technical task / User Story / Bug …) with a Markdown description, parent link, area/iteration, and tags, in a single `az rest` call. Trigger when the user says "create azdo ticket", "new work item", "create technical task", "child ticket under #N", or asks to spawn a follow-up ticket from code or plan context. Use INSTEAD OF `az boards work-item create` whenever the description should render as Markdown (that command cannot pass the format flag).
ticket
Transition Azure DevOps work item state. Trigger when user says "ticket <id> active", "set ticket cr", "/dev-azdo:ticket", or wants to move a work item between states (active, code-review, ready, closed).
nuxt
This skill should be used when working on Nuxt projects (v3+). Use it for building Vue applications with Nuxt's file-based routing, server-side rendering, and auto-import features. Trigger when working with .vue or .ts files in Nuxt directories (pages/, server/, composables/, middleware/), nuxt.config.ts, or when the project contains a nuxt dependency in package.json. Also trigger for questions about Nuxt concepts like composables, auto-imports, server routes, SSR/SSG patterns, or file-based routing.
video-to-article
Use this skill when the user wants to convert a lecture, presentation, or talk video into text formats (transcript, outline, or article). Trigger when user mentions processing video recordings, creating transcripts from lectures, or generating articles from recorded presentations.
agent-browser
Automate a real browser with the agent-browser CLI — open pages, snapshot interactive elements, click/fill by ref, extract content. Use when the user wants to browse, open a page, visit a URL, navigate a site, click or fill a form element, scrape, take a screenshot of a page, test a web app, or says "agent-browser". Works as a general-purpose browser automation tool in any repo, even ones without a local browser skill installed.
wait-what
Stop — that last message did not land. Re-pitch it in plain language.
triage
Triage requirements, specs, or tickets. Detect input (pasted text, markdown path, tracker ticket id/URL, or empty prompt). Explore codebase + docs, score completeness, ask clarifying questions, write a markdown report. Trigger when user says "triage", "review this spec", "is this requirement complete", or provides a ticket/spec to assess.
to-tickets
Break a plan, spec, or the current conversation into vertical-slice tickets, each declaring its blocking edges.
to-spec
Turn the current conversation context into a spec. Use when user wants to create a spec (or PRD) from the current context.
tdd
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
implement
Implement work from a ticket, spec, or inline description; auto-detects the next item from the task folders when no argument is given.
grill-with-docs
Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (GLOSSARY.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.
code-review-diff
Review code changes from the current branch, staged changes, a git ref, or a diff/patch file. Pure git-native — no platform/PR awareness. Trigger when user says "review this", "review diff", "/aiwork:code-review-diff", or provides a git ref or diff path. Read-only — never posts comments.
aiwork-protocol
Structure AI work artifacts under .aiwork/{YYYY-MM-DD}_{slug}/ folders using the project's protocol (triage, research, spec, prd, plan, review, notes, docs/). Use when the user asks to plan, make a spec, triage, research a task, write a report, code review, summarize findings, save the work, document decisions, record this, write that down, persist findings, or references any path under .aiwork/. Also use when starting a non-trivial task that needs a plan or spec before implementation, or when finishing one and capturing notes.
browser-tools
Use this skill when the user asks to test, verify, interact with, or automate web pages and browsers. Trigger for requests involving Chrome automation, browser testing, web scraping, screenshot capture, element selection, or checking web applications. Also trigger when user mentions "browser tools" explicitly.
code-review
Review code changes from current branch, an Azure DevOps PR, a git ref, or a diff/patch file. Trigger when user says "review this", "code review", "/df:code-review", or provides a PR id/URL, ticket URL, git ref, or diff path. Read-only — never posts comments.
changelog
Show recent Claude Code changes personalized to user's setup. Trigger when user asks about changelog, "what's new", "cc changelog", "claude code updates", "recent changes", or wants to know what changed in Claude Code.
scf-worker
云函数工程师,负责腾讯云 SCF 无服务器函数开发。遵循最小权限、幂等、重试+死信、可观测性工程基线。处理 COS 直传签名、回调处理、媒体转码、Webhook 转发、批处理任务。适用于收到 SCF 部门任务卡(如 CMS-S-001)或修复类任务卡时使用。
qa-acceptance
质量验收专家,从用户视角验证交付物可用性/正确性/性能/回归。遵循阻断不合格交付、脚本化验证、数据隔离、覆盖验收标准的工程基线。使用 Playwright(E2E)、Jest+Supertest(API)、k6(性能)等工具。适用于收到 QA 部门任务卡(如 CMS-Q-001)或需要验收交付物时使用。
frontend-dev
前端开发专家,负责 Next.js 14 App Router + React 18 + TypeScript + Ant Design + Zustand 前端应用开发。遵循契约驱动、统一UI规范、访问控制、可测试性工程基线。处理登录鉴权、动态表单、内容管理UI、E2E测试。适用于收到 Frontend 部门任务卡(如 CMS-F-001)或修复类任务卡时使用。
reviewer
代码审查员,守护质量闸口。对所有部门(Backend/Frontend/SCF/Deploy)的 PR 进行安全、性能、正确性、可维护性、可观测性的系统性审查。遵循证据先行、问题分级、签发修复卡、独立克制的工程基线。适用于收到任一部门提交 PR 或需要质量把关时使用。
backend-dev
后端开发专家，负责 Express.js + Knex.js + MySQL 8 + Redis 后端服务开发。遵循 OpenAPI 先行、TDD 推动、RBAC 安全、可观测性工程基线。处理 Provider 动态加载、缓存系统、数据库设计、内容管理 API 开发。适用于收到 Backend 部门任务卡（如 CMS-B-001）或修复类任务卡时使用。
product-planner
AI产品经理,整套"0基础 AI 协同开发系统"的源头角色与项目总导演。将自然语言需求转换为可执行的产品规划与标准化任务卡,协调 Backend/Frontend/SCF/QA/Reviewer/Deploy/Billing Guard 多部门有序并行交付。遵循易用性优先、契约优先、门禁治理、MVP-first 的工程基线。适用于收到自然语言需求时使用。
billing-guard
计费审计专家,在规划/开发/运行阶段持续审计与优化成本。评估任务卡预算、模拟调用成本、监控高成本路径,在超出预算或异常时阻断执行并提出替代方案。遵循数据驱动、三板斧优化(缓存/批量/降级)、预警阻断的工程基线。适用于规划预审、PR成本审查、运行时监控时使用。
codebuddy-deploy
部署与运维专家,负责把通过 Reviewer 与 QA 门禁的构建安全、可回滚、可观测地部署到服务器(PM2 三进程 + Nginx 反代 + 宝塔)。遵循零停机部署、健康检查、回滚≤3分钟、发布后冒烟的工程基线。处理部署编排、配置管理、流量管理、监控告警。适用于收到 Deploy 部门任务卡或需要发布上线时使用。
skill-creator
Create and refine Codex skills (folders containing `SKILL.md`). Use when you need help naming a skill, writing effective `name`/`description`, structuring the on-disk instructions, or adding scripts/references/assets for repeatable workflows.
digital-samba
Build video conferencing integrations using Digital Samba's API and SDK. Use when creating meeting rooms, embedding video calls, generating participant tokens, managing recordings, or integrating real-time collaboration features. Triggers include "Digital Samba", "video conferencing API", "embed video calls", "meeting room integration", "WebRTC iframe", "participant tokens".
cli-ninja-tools
CLI power tools for AI-assisted development. Use when (1) needing recommendations for CLI tools to install, (2) processing JSON/YAML data with jq/yq, (3) searching code with ripgrep or ast-grep, (4) documenting a CLI tool or multi-tool recipe you've discovered, (5) wanting to learn CLI patterns for data pipelines, or (6) setting up a new project and want CLI recommendations. Supports three modes - init (project scan), document (capture new recipes), and recommend (codebase analysis).
obsidian-skill
Expert guidance for working with Obsidian vaults including Obsidian Flavored Markdown (OFM) syntax, organization best practices, daily/weekly task workflows, vault maintenance, and automation. This skill should be used when working with Obsidian notes, organizing vault structure, setting up task management workflows, or integrating with Obsidian tooling.
test-development
Create comprehensive test suites by discovering and adapting to any testing framework, following project test patterns and ensuring robust coverage. Use when writing tests, improving coverage, validating functionality. Triggers: 'test', 'coverage', 'unit test', 'integration test', 'E2E', 'spec', '테스트', '커버리지', '단위 테스트', '통합 테스트', '테스트 작성', working with *.test.*, *.spec.*, test/, __tests__/.
code-implementation
Implement code changes by learning from and precisely matching existing codebase patterns, ensuring seamless integration with surrounding code. Use when writing new features, modifying logic, adding functionality. Triggers: 'implement', 'write code', 'add feature', 'create', 'build', 'fix bug', '구현', '코드 작성', '기능 추가', '생성', '빌드', '버그 수정', '만들어', working with *.ts, *.go, *.java, *.py, *.nix, *.rs files.
architectural-planning
Create detailed technical plans and implementation roadmaps by analyzing project architecture and designing solutions that integrate seamlessly with existing patterns. Use when designing features, planning integrations, making architectural decisions. Triggers: 'plan', 'design', 'architecture', 'approach', 'how should I', 'best way', 'integrate', '계획', '설계', '아키텍처', '접근법', '어떻게 해야', '가장 좋은 방법', '통합', '마이그레이션', working with multi-module features, system boundaries, complex migrations.
a2a-workflow
Orchestrate complex repository work through scoped research, architecture, planning, single-writer implementation, independent verification, targeted repair, and compact handoff. Use for multi-file, risky, ambiguous, architectural, migration, security-sensitive, or explicitly requested A2A tasks. Do not use the full workflow for trivial edits.
example-skill
Example skill - Claude will autonomously use this based on the description. Describe what this skill does and when to use it.
linear-discipline
Use this skill when discussing code changes, implementation work, feature status, or when starting/completing development tasks. Reminds about Linear issue tracking discipline - always having an issue in progress before writing code, marking work as done, and creating issues for unexpected scope. Triggers when users mention implementing features, writing code, or checking on work status.
vertical-slice-planning
Use this skill when discussing feature breakdown, PR structure, implementation ordering, or how to decompose work. Guides thinking about vertical slices (end-to-end functionality) rather than horizontal layers (all of one layer first). Triggers on "how should we break this down?", "what order should we implement?", "how many PRs?", or decomposition discussions.
mvp-scoping
Use this skill when discussing features, planning work, or when users describe what they want to build. Guides MVP thinking - focusing on "what's the minimum to make this work?" rather than comprehensive solutions. Triggers on phrases like "help me think through this feature", "what should we build first?", "how should we scope this?", or any feature planning discussion.
create-agent
Create a new Claude Code custom agent (subagent). Use when the user asks to "create an agent", "make an agent", "new agent", "build an agent", "create a subagent", "/create-agent", or says something like "create an agent for that" referencing something in the conversation.
1password
Use when needing to fetch, read, store, or manage secrets and credentials. Triggers on "get secret", "fetch password", "store credential", "1password", "op read", "vault", or when a task requires API keys, tokens, or passwords that might be in 1Password.
cloudflare-api
Manage Cloudflare via API — DNS records, tunnels, Pages, zones. This skill should be used when creating or updating DNS records, managing Cloudflare tunnels, deploying to Cloudflare Pages, listing zones, or any Cloudflare API interaction. Triggers on "cloudflare", "DNS record", "tunnel", "cloudflare pages", "CNAME", "zone".
issue-writing
Use this skill when writing, reviewing, or discussing issue descriptions, acceptance criteria, or task breakdowns. Ensures consistent, high-quality issue structure that any developer or AI can pick up and execute. Triggers when drafting issues, defining requirements, or when users ask "how should I write this issue?" or "what should the acceptance criteria be?"
graphite-workflow
Use this skill when working with Graphite (gt) for stacked PRs, using execute-issue-graphite agent, or when the user mentions Graphite, stacking, or gt commands. Ensures proper use of gt commands instead of raw git for stack-aware operations.
supabase-seeding
Guides proper Supabase database seeding patterns. Use when creating seed files, seeding data, populating databases, or setting up test data in Supabase projects. Covers local and production seeding best practices.
atomic-design-planning
Use this skill when discussing UI components, design systems, frontend implementation, or component architecture. Guides thinking about Atomic Design methodology - atoms, molecules, organisms - and promotes component reuse over creation. Triggers on UI/frontend discussions, "what components do we need?", "should I create a new component?", or design system questions.
curl-api
Make HTTP API requests with curl. Use when calling REST APIs, making HTTP requests, testing endpoints, or working with web services via curl.
view-refactor
Refactor SwiftUI view files for consistent structure, dependency injection, and Observation usage. Use when asked to clean up a SwiftUI view's layout, handle view models safely, or standardize how dependencies are initialized and passed.
Page 1344 of 1714 · 85683 results
