3천건 · 관련도순
GitHub operations via `gh` CLI: issues, PRs, CI runs, code review, API queries. Use when: (1) checking PR status or CI, (2) creating/commenting on issues, (3) listing/filtering PRs or issues, (4) viewing run logs. NOT for: complex web UI interactions requiring manual browser flows (use browser tooling when available), bulk operations across many repos (script with gh api), or when gh auth is not configured.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Analyze all github issues. Use when the user says 'triage the github issues' or 'analyze open github issues'.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Guides creation and validation of custom dotnet new templates. Generates templates from existing projects and validates template.json for authoring issues. USE FOR: creating a reusable dotnet new template from an existing project, validating template.json files for schema compliance and parameter issues, bootstrapping .template.config/template.json with correct identity, shortName, parameters, and post-actions, packaging templates as NuGet packages for distribution. DO NOT USE FOR: finding or using existing templates (use template-discovery and template-instantiation), MSBuild project file issues unrelated to template authoring, NuGet package publishing (only template packaging structure).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Complete Flutter SDK installation, IDE configuration, and troubleshooting guide for Linux, macOS, and Windows. Use for installing Flutter SDK from scratch, configuring PATH environment variables across platforms, setting up VS Code/Android Studio/IntelliJ IDEA with Flutter plugins, resolving 'flutter command not found' errors, fixing flutter doctor warnings and errors, troubleshooting Android SDK/NDK installation issues, configuring Xcode and CocoaPods on macOS, installing Visual Studio C++ build tools on Windows, resolving PATH conflicts and SDK path issues, fixing network/proxy setup problems, debugging IDE plugin activation, configuring emulators and simulators, handling platform-specific build errors, resolving dependency conflicts, fixing certificate and signing issues, troubleshooting hot reload failures, and verifying successful installation with flutter doctor diagnostics.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
AI-powered codebase security scanner that reasons about code like a security researcher — tracing data flows, understanding component interactions, and catching vulnerabilities that pattern-matching tools miss. Use this skill when asked to scan code for security vulnerabilities, find bugs, check for SQL injection, XSS, command injection, exposed API keys, hardcoded secrets, insecure dependencies, access control issues, or any request like "is my code secure?", "review for security issues", "audit this codebase", or "check for vulnerabilities". Covers injection flaws, authentication and access control bugs, secrets exposure, weak cryptography, insecure dependencies, and business logic issues across JavaScript, TypeScript, Python, Java, PHP, Go, Ruby, and Rust.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Interact with GitHub using the `gh` CLI. Use `gh issue`, `gh pr`, `gh run`, and `gh api` for issues, PRs, CI runs, and advanced queries. Use when the user asks about GitHub issues, pull requests, workflows, or wants to interact with GitHub repositories from the command line — including tasks like check CI status, create PR, list issues, or query the GitHub API.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Interactive QA session where user reports bugs or issues conversationally, and the agent files GitHub issues. Explores the codebase in the background for context and domain language. Use when user wants to report bugs, do QA, file issues conversationally, or mentions "QA session".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Investigates a session recording by gathering metadata, person profile, same-session events, and linked error tracking issues in one pass. Use when a user provides a recording or session ID and wants to understand what happened — who the user was, what they did, what errors occurred, and whether there are related error tracking issues. Replaces the manual chain of session-recording-get, persons-retrieve, execute-sql, and query-error-tracking-issues-list.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
プロジェクトのドラフトアイテム (DraftIssue) を実 GitHub Issue に変換し、Status/Priority/Size 等のフィールド値を引き継ぐ。親 Issue を指定または新規作成して `gh api .../sub_issues` で sub-issue として紐付け可能。「ドラフトを Issue 化」「DraftIssue を変換」「プロジェクトのタスクを Issue にして」などで使用。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Sentry の Issue 一覧 URL（例 `https://<org>.sentry.io/issues/?project=<id>&environment=<env>`）を受け取り、未解決（unresolved）の Issue を列挙して1件ずつサブエージェントで並列調査する。コード上で既に解消済みと確認できたものは Sentry 側を resolved にし、未解消のものは `create-issue` スキルで GitHub Issue を作成する。「Sentryのissueをトリアージして」「Sentryの未解決エラーをチケット化して」といった依頼で使用する。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Debug Spring Boot issues systematically. Use when encountering bean errors like NoSuchBeanDefinitionException, circular dependency issues, application startup failures, JPA/Hibernate problems including LazyInitializationException and N+1 queries, security misconfigurations causing 403 Forbidden errors, property binding failures, CSRF token issues, or any Spring Boot application requiring diagnosis with Actuator endpoints and JVM debugging.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create, manage, triage, and close GitHub issues. Search existing issues, add labels, assign people, and link to PRs. Works with gh CLI or falls back to git + GitHub REST API via curl.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when an approved PRD roadmap must go to GitHub — 'publicar o roadmap no GitHub', 'criar o project e as issues do PRD', 'publish PRD roadmap' — handing over to pwdev-github (Project from a template, issues, sub-issues, blocked-by). Do NOT use for a single issue with the whole PRD (prd-export).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Cria, atualiza, comenta, fecha e reabre issues do GitHub e gerencia as tarefas de um GitHub Project — mover Status, editar campos, sub-issues e dependências "blocked by", inclusive em lote. Use quando o usuário disser "criar issue", "abrir uma issue", "fechar a issue #12", "reabrir", "comentar na issue", "atribuir para", "mover para Em andamento", "marcar como concluída", "bloqueada por", "sub-issue", "o que está bloqueando", "tarefas do project", "fechar as tasks da feature", ou citar #123 num repo GitHub. Não use para criar um Project novo (skill github-project) nem para publicar um roadmap inteiro (skill github-publish).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tags review," "SEO health check," "my traffic dropped," "lost rankings," "not showing up in Google," "site isn't ranking," "Google update hit me," "page speed," "core web vitals," "crawl errors," or "indexing issues." Use this even if the user just says something vague like "my SEO is bad" or "help with SEO" — start with an audit. For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema-markup. For AI search optimization, see ai-seo.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Triage issues through a state machine driven by triage roles. Use when user wants to create an issue, triage issues, review incoming bugs or feature requests, prepare issues for an AFK agent, or manage issue workflow.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create, triage, label, assign GitHub issues via gh or REST.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Run a conversational QA session where the user reports bugs or issues, and file durable Beads issues using project domain language. Use when the user wants to report bugs, do QA, file issues conversationally, or mentions a QA session.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
[BETA] Detect, review, and fix code-quality and correctness issues in an AEM as a Cloud Service project — locally, with no external services or network calls. Use whenever a user wants to check, review, assess, audit, scan, modernize, upgrade, or fix AEM Java, Sling Models, OSGi, or Maven code — for example: "check my Sling Models are implemented correctly", "review my @Inject usage", "are my Maven dependencies up to date", "scan this AEM project for issues", "modernize my Sling Models", or "fix code-quality problems". Name the files to assess, or ask it to scan the repo; it detects issues, plans, and — only when you ask — applies surgical edits on a branch or in place, then verifies with mvn compile. It recognises the intent and handles each issue type itself, reporting anything it cannot yet fix. This skill is in beta. Verify all outputs before applying them to production projects.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
현재 소스와 테스트 결과를 바탕으로 OpenClaw 이슈와 풀 리퀘스트를 조사하고 검토합니다. 허용된 범위에서 수정부터 합병 완료 확인까지 진행합니다.
공개 전 글이나 코드를 두 독립 에이전트가 같은 기준으로 심사합니다. 모두 통과할 때까지 수정과 재심사를 반복하고, 반복 한도에 도달하면 미해결 문제를 사람에게 넘깁니다.
제공된 글 예시나 브랜드 문체에 맞춰 기사, 가이드, 뉴스레터를 작성합니다. 메모와 조사 자료를 글로 정리하고 기존 원고의 구성과 근거도 검토합니다.
RSS, JSON API, GitHub를 주기적으로 확인하고 기록된 ID와 비교해 새 항목만 추출합니다. 업데이트가 없으면 알림을 보내지 않는 모니터링을 구성합니다.
기능 추가와 코드 정리, 풀 리퀘스트 검토를 OpenAI Codex CLI에 맡깁니다. 오래 걸리는 작업의 진행 확인과 여러 문제를 병렬로 수정하는 절차도 다룹니다.