3.2K skills · sorted by relevance
Turn GitHub issue reports into actionable work by searching for duplicates, attempting reproduction, and assessing user impact. Organize issues with existing labels, appropriate owners, and milestones, while clearly recording what was and was not verified.
Create developer tutorial slides with a GitHub-style dark background, purple and blue lighting effects, and three-color gradient headings. Coordinate code colors, centered layouts, and highlighted blocks within a 16:9 presentation.
Audits GitHub Actions workflows that run AI coding agents. Traces how attacker-controlled content reaches prompts, checks permissions and sandbox settings, and reports evidence, severity, and fixes for prompt injection and related configuration risks.
Prepare local iPolloWork changes for GitHub while staying on the current personal branch. Preserve edits, sync from main, report conflicts, commit and push changes, and create a pull request when requested.
Publish selected local changes to GitHub by checking their scope, creating a branch when needed, committing files, and pushing them. Create a draft pull request, a proposed change awaiting review, and report checks and remaining risks.
Turn a Seed specification into GitHub issues for team planning. The skill creates a parent issue and implementation tasks, distributes acceptance criteria across them, and links the tasks in a progress checklist.
Check CI, the automated checks run on code changes, for the current branch alongside recent commits. Supports GitLab CI and GitHub Actions, with optional pull request or merge request numbers and links when command-line tools are unavailable.
Plan task handoffs between agents on different machines using Git to share YAML task and result files. This implementation specification describes validation, execution limits, result reporting, and GitHub Issues as an additional route for urgent requests.
Review GitHub security advisories, verify fixed versions, and update compatibility rules with narrowly scoped changes. Document upgrade steps and check that version blocking, warnings, and related configuration behave as intended.
Check GitHub pull request review comments against the actual code. Classify findings as valid, invalid, or partially valid, identify similar issues elsewhere, and produce recommended actions, with optional replies after user approval.
Review CI/CD pipelines, the workflows that build and release software, for unsafe code execution, exposed secrets, and excessive permissions. Combine automated scanning with manual checks to document reproducible findings and suggested fixes.
Approve a GitHub account to open pull requests in get-bb/bb by updating its allowlist. The workflow verifies the account, checks the change, and creates and merges an approval PR while skipping SlopCop review and CI.
Review unresolved GitHub pull request comments against the current code, apply minimal fixes for valid issues, and reply to review threads. Comments that need human judgment remain open, while fixed or unnecessary requests are resolved with explanations.
Resolve an identified GitHub issue through investigation, duplicate-work checks, implementation, and regression testing. Open a pull request, address CI and review feedback, and track the outcome while keeping the issue updated with concise progress comments.
Extract writing feedback from GitHub pull request reviews and compare original wording with suggested revisions. Analyze first and final drafts to identify recurring lessons about clarity, grammar, tone, and structure for future writing.
Search Wayback Machine archives for deleted GitHub files, issues, pull requests, and wiki pages. Recover available text and repository details from saved web pages to investigate a project's past state.
[omh] Chat report that should become a GitHub issue: turn a public chat report into a confirmed, verified issue package. Use when the user says: github-issue-intake, github issue intake, issue intake, file this as an issue, file a github issue, open a github issue, create a github issue, submit a github issue.
The English summary is being prepared. Showing the original description.
🇺🇸 Product Launch & Product Hunt #1 Playbook — Multi-channel launch timing and sequencing. T-14 warm-up → T-0 launch day → T+7 momentum. Hunter selection, maker comment templates, comment cadence, anti-shadowban rules. Distilled from 30+ Product Hunt #1 daily launches across 150+ AI startups. **Supports 3 product paths: developer/maker (PH+GitHub), B2C consumer (Reddit/communities/TikTok, skip PH), B2B (LinkedIn+media).** 🇨🇳 产品发布与 Product Hunt 夺冠手册 — 多渠道发布的时序与节奏。T-14 预热 → T-0 发布日 → T+7 后续。Hunter 选择、maker comment 模板、评论节奏、防 shadowban。提炼自 30+ 次 Product Hunt 日冠、150+ AI 创业公司实战。**支持三种产品路径：开发者/maker（PH+GitHub）、2C 消费者（社区种子/TikTok，跳过 PH）、B2B（LinkedIn+媒体）。** 🇯🇵 プロダクトローンチ＆Product Hunt 1位プレイブック — マルチチャネルのローンチ時系列。T-14準備→T-0当日→T+7モメンタム。ハンター選定、メーカーコメント、コメントリズム、シャドウバン回避。**3つの製品パス対応：開発者/maker（PH+GitHub）、2C消費者（コミュニティ種・TikTok、PHスキップ）、B2B（LinkedIn+メディア）。** 🇰🇷 제품 출시 & Product Hunt 1위 플레이북 — 멀티채널 출시 타이밍과 시퀀싱. T-14 워밍업 → T-0 출시일 → T+7 모멘텀. 헌터 선정, 메이커 코멘트, 댓글 리듬, 섀도밴 방지. **3가지 제품 경로 지원: 개발자/maker(PH+GitHub), 2C 소비자(커뮤니티 씨드/TikTok, PH 건너뜀), B2B(LinkedIn+미디어).** Triggers: "product launch" | "launch strategy" | "Product Hunt" | "PH launch" | "how to launch" | "go to market" | "GTM" | "launch day" | "find a hunter" | "maker comment" | "launch sequencing" | "发布策略" | "产品发布" | "发 PH" | "Product Hunt 准备" | "找 hunter" | "ローンチ" | "출시 전략"
The English summary is being prepared. Showing the original description.
Find existing skills before building a new one. Search local installations, marketplaces, GitHub, and the web, then review candidates for relevance and risky behavior to help choose between reuse, extension, and fresh creation.
Build end-to-end tests that operate Windows desktop apps through pywinauto and Windows UI Automation, an interface for accessing screen controls. Covers stable element selection, waits, failure screenshots, test isolation, and CI setup for native applications.
Investigate unexpected costs in the ECC Tools GitHub App by tracing events, queued jobs, analysis workers, and billing logic. Identifies repeated pull request creation, usage-limit bypasses, unintended premium-model calls, and duplicate retries, then verifies targeted fixes.
Build Playwright tests that reproduce browser interactions, organize reusable page operations, and run checks automatically. Investigate tests that fail inconsistently, and save screenshots, videos, and execution traces to help diagnose failures.
Coordinate a complete Paperclip release, from candidate verification and canary testing to stable npm publication and GitHub Release creation. Track release notes, Docker smoke tests, announcement follow-up, and linked content cases when Cases are enabled.
Help DeerFlow maintainers investigate GitHub issues and review pull requests, or proposed code changes. It prepares or posts evidence-based comments with fix strategies, risks, and validation guidance, and compares competing proposals for the same issue.