3.2천건 · 관련도순
Install Codex skills into $CODEX_HOME/skills from a curated list or a GitHub repo path. Use when a user asks to list installable skills, install a curated skill, or install a skill from another repo (including private repos).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Teach software development through active project work while still producing a working result, maintaining bilingual English and Chinese project documentation, protecting private context, and publishing reviewed updates to GitHub only after confirmation. Use when Codex helps the user create, build, extend, debug, refactor, document, publish, or understand a software project and the user's goal includes learning, mentorship, guided implementation, pair programming, understanding the code, or becoming able to do similar work independently.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Review and resolve PR issues with Qodo - get AI-powered code review issues and fix them interactively (GitHub, GitLab, Bitbucket, Azure DevOps)
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Review and resolve PR issues with Qodo - get AI-powered code review issues and fix them interactively (GitHub, GitLab, Bitbucket, Azure DevOps)
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Find niches, topics, audiences, products, channels, and content angles via deep web search. Use whenever Ahmad says "find me a niche", "hunt niches in X", "what's an underserved audience for Y", "find similar sites/videos to <example>", "research the X market", "what are people building in Y space", "/niche-hunter X", or any phrasing that asks for niche / market / topic / audience / product / channel discovery across the open web. Trusts domain + keyword search; chains web_search → web_fetch / web_extract / web_crawl + reddit_search + search_youtube + github_repo_intel. NEVER uses awesome-list shortcuts. Output shape is FLEXIBLE — list, table, report, suggestions, or normal prose — picked from how Ahmad phrased the ask.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Policy-enforcing installer that deploys hardened Claude Code Action workflows (`@claude` manual mention + dependency-bot auto-fix) into a personal GitHub repository the user administers. Use when asked to introduce Claude Code Action, apply `@claude` mention support, or set up automated CI auto-fix for dependency bot PRs, using the security-hardened templates shipped with this skill.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use to file a GitHub issue when a finding needs its own work order or the operator asks; OBPI corrections stay in its change log.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Give a project a GitHub-releases updater. Use when a release ships unoffered, or a hand-copied updater moves to vendor/.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Orchestrate autonomous AI development pipelines through your Kanban board (Asana, GitHub Projects, Linear). Manages multi-worker Claude Code dispatch, deterministic quality gates, adversarial review, per-task cost tracking, and crash-proof pipeline execution.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Detect Git remote URL for GitHub integration
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Convert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Fetch GitHub issues, spawn sub-agents to implement fixes and open PRs, then monitor and address PR review comments. Usage: /gh-issues [owner/repo] [--label bug] [--limit 5] [--milestone v1.0] [--assignee @me] [--fork user/repo] [--watch] [--interval 5] [--reviews-only] [--cron] [--dry-run] [--model glm-5] [--notify-channel -1002381931352]
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
AI agent integration layer for the Pump SDK — agent instruction files, .well-known discovery, LLM context documents, 15+ skill files, MCP server prompts, and terminal management rules for GitHub Copilot and Gemini.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Turn a fix you made for a whole class of bugs into help for others: reverse-search GitHub for people hitting the same symptom, pick the 3-5 best live threads and post one tailored answer or gist each, no copy-paste fan-out. Use after a verified class fix. Triggers: /share-fix, /sf, share the fix.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Open-source one slice of a private system: take a component, sanitize it, run a leak-scan as a hard gate, publish to GitHub, then changelog, roadmap and tag on cadence, then the content wave. Publishing without passing the leak-scan is forbidden. Triggers: "/release-slice <piece>", "ship the next slice".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Find live third-party GitHub issues and discussions on topics where you have real hands-on experience and artifacts, then reply with that experience to build reputation. Use when asked to answer people about your work, find threads matching your expertise, or reply with evidence from your own setup.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Дверь к банку шуток Майкрофта: подобрать строку раскрытия/ответку/гэг под конкретный текст и канал. Триггеры: '/mycroft-joke', '/mj', 'шутка майкрофта', 'смешное раскрытие', 'ответь хеклеру', а также САМ — каждый раз, когда пишу исходящее от лица Майкрофта (ФА, личка, GitHub-треды, комменты) и ставлю строку раскрытия §3.3: сухая плашка = дефект, строка берётся из банка
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
- СОРСИНГ ПОД РЕЙЗ в два трека: инвесторы из нашего VC-графа (leads.db) и покупатели-пилоты, найденные ПО СИМПТОМУ в интернете (GitHub issues, Hacker News, X, наши же репозитории, клуб СОСТАВ). Триггеры: “/raise-sourcing“, “/sourcing“, “собери список инвесторов“, “кому питчить“, “найди покупателей“, “добери лидов под рейз“, “кого звать в пилот“, “обнови стол сорсинга“, “raise sourcing“
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Answer reviewers on your own pull requests in other people's repos: find threads where the ball is on your side, tell humans from bots, do exactly what was asked and reply with evidence. Use at the start of any GitHub session or on a new-review alert. Triggers: /pr-reply, /prr, answer the reviewers, who is waiting on us.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Write an evergreen teaching longform for non-technical readers built from your own real material (systems you run, dated failures, numbers), structured as a stitched lesson that can live as a blog post, a GitHub guide hub and a newsletter issue. Use when turning lived engineering experience into a durable how-to. Triggers: /guide, make a guide, build a lesson, evergreen guide.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build a dashboard from idea to live link in one pass: create the visualization, file it in one shared catalog, cross-link it with the others, publish to GitHub Pages and return the working URL right away. Use when results carry more than one fact to decide on. Triggers: /dash, build a dashboard, show it visually, publish the dashboard, give me the dashboard link.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
After shipping a repo, release or feature, find who on GitHub actually needs it: search issues, discussions and catalogs for the symptom, rank live threads and draft one precise reply per consumer. Use right after any artifact goes public. Triggers: /consumer-hunt, /ch, find consumers, where to submit.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Finds free backlink and brand mention opportunities across Hacker News, Quora, GitHub, directories, and niche communities. Outputs a prioritized action plan with draft responses ready to post. Use after brand research and content creation to amplify reach and AI engine citations.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Prose final-pass editor for GitHub issue bodies, pull request bodies, release notes, README/docs changes, public comments, and user-facing explanations. Use when Codex drafts or revises substantial prose that will be published or committed, especially when the user asks to polish, de-slop, make it less AI-written, improve a PR/issue body, or prepare docs text; do not use for ordinary code implementation, debugging transcripts, logs, quoted text, command output, API names, or Chinese conversational replies unless explicitly requested.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.