1.2천건 · 관련도순
Handle pull requests and review comments using GitHub CLI (gh). Use when the user wants to check PR comments, address review feedback, reply with commit hashes, or work with pull requests.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use whenever the screens, UX, wording, feedback after actions, accessibility, or layout of frontend/ come up, even without the word "review" — delegates to the frontend-ux-reviewer agent, which runs the dev screens against the Lean CLI with Playwright and reports with evidence. Not for reviewing the domain model itself (that is the ddd skill's review).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Automatically consume open GitHub issues one by one. Fetches the oldest open issue, delegates implementation to the issue-implementer agent, runs code review via the code-reviewer agent, iterates on feedback, merges the PR, and moves on to the next issue. Invoke with `/auto-issue-worker`.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generates and maintains competitive battlecards from win/loss data, competitor intel, G2 reviews, and sales feedback. Use when building battlecards for a specific competitor, updating existing battlecards with new intel, preparing BDRs or AEs for competitive deals, analyzing win/loss patterns against a competitor, or responding to a competitor's product launch or pricing change. Also use when asked to "build a battlecard," "update competitive intel," "how do we beat [competitor]," "what do we say when a prospect mentions [competitor]," or "analyze our win/loss against [competitor]." Designed for B2B SaaS teams selling against known competitors in deals with multi-persona buying committees.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Disciplined diagnosis workflow for hard, intermittent, or multi-component bugs and performance regressions: inspect logs and existing evidence, build a feedback loop, test falsifiable hypotheses, instrument gaps, and verify the outcome. Use when the root cause is unclear, reproduction is unreliable, several causes or components are plausible, or performance has regressed. Do NOT use for obvious single-cause errors, straightforward configuration or syntax fixes, planned feature work, or broad architecture review. Diagnosis-only requests stop after reporting the root cause and evidence; apply a fix only when the user requested one.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Implement a phishing report button in email clients with automated triage workflow that analyzes user-reported suspicious emails and provides feedback to reporters.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Analyzes meeting transcripts and recordings to uncover behavioral patterns, communication insights, and actionable feedback. Identifies when you avoid conflict, use filler words, dominate conversations, or miss opportunities to listen. Perfect for professionals seeking to improve their communication and leadership skills.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Assists in writing high-quality content by conducting research, adding citations, improving hooks, iterating on outlines, and providing real-time feedback on each section. Transforms your writing process from solo effort to collaborative partnership.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Run the full implement-review-fix loop using implementer and reviewer personas. Supports effort-based multi-reviewer scaling (1-5 reviewers) with automatic specialization selection. Includes memory-based feedback loop that learns from past review patterns. Loops until all reviewers find 0 issues of any severity.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Plan a user interview topic in PostHog — pick who to target (cohort, emails, or PostHog distinct IDs), draft what to ask about, and prepare the voice-agent context plus a question list. Use when the user asks to "talk to users", "check how users feel about X", "interview some customers", "set up a user interview", "run a user-research call", "find users to ask about Y", or otherwise wants qualitative feedback through a conversation. Walks the user through targeting (cohorts-list, persons-list, or accepting emails / distinct IDs directly), captures the topic, and prompts for agent context and questions before calling user-interview-topics-create. Cohort targeting is resolved to explicit emails/distinct_ids at create time — topics snapshot their audience and do not re-evaluate cohort membership later. Do NOT trigger when the user is uploading a recorded interview audio file (that's the separate UserInterview/transcript flow) or only browsing existing topics with user-interview-topics-list.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Perform code reviews following Sentry engineering practices. Use when reviewing pull requests, examining code changes, or providing feedback on code quality. Covers security, performance, testing, and design review.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Fine-tune LLMs using reinforcement learning with TRL - SFT for instruction tuning, DPO for preference alignment, PPO/GRPO for reward optimization, and reward model training. Use when need RLHF, align model with preferences, or train from human feedback. Works with HuggingFace Transformers.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Evaluate an interface from a UX perspective, assessing hierarchy, information architecture, emotional resonance, cognitive load, and overall quality with evidence-linked judgments and actionable feedback. Use when the user wants an overall design or UX review—not when the main need is measurable accessibility/performance diagnosis, or final micro-detail polish.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Add or refine depth through elevation systems, raised and inset surfaces, layered overlap, and meaningful shadow behavior so interfaces feel structured instead of flat. Use when the user mentions depth, elevation, shadows, layering, flat cards, pressed states, drag feedback, or inset controls.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Apple's approach to interface design and fluid, physical motion, translated for the web. Use when building or reviewing gesture-driven UI, spring animations, drag/swipe/sheet interactions, momentum and interruptible transitions, translucent materials and depth, typography (optical sizing, tracking, leading), reduced-motion, or the design foundations (feedback, spatial consistency, restraint) behind Apple-style interfaces.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
When the user wants to edit, review, or improve existing marketing copy. Also use when the user mentions 'edit this copy,' 'review my copy,' 'copy feedback,' 'proofread,' 'polish this,' 'make this better,' or 'copy sweep.' This skill provides a systematic approach to editing marketing copy through multiple focused passes.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design, implement, and review web interface layout, component states, feedback, and motion within the current CodeConductor workflow. Use for concrete web UI work or requested UI audits, not backend-only tasks or native mobile apps.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Improve test value and feedback cost when auditing slow, flaky, redundant or brittle tests; choosing tests during implementation; or reviewing test changes before a commit or PR. Keep ordinary implementation and pre-commit use scoped to the affected behavior, not a repository-wide audit.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Fine-tune LLMs using reinforcement learning with TRL - SFT for instruction tuning, DPO for preference alignment, PPO/GRPO for reward optimization, and reward model training. Use when need RLHF, align model with preferences, or train from human feedback. Works with HuggingFace Transformers.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use this skill when the user requests to review, analyze, critique, or summarize academic papers, research articles, preprints, or scientific publications. Supports comprehensive structured reviews covering methodology assessment, contribution evaluation, literature positioning, and constructive feedback generation. Trigger on queries involving paper URLs, uploaded PDFs, arXiv links, or requests like "review this paper", "analyze this research", "summarize this study", or "write a peer review".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when work needs reviewing before it is merged, and when review feedback has arrived and needs acting on
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Revisa e melhora copy existente através de 7 passes focados (clareza, voz, e daí, prove, especificidade, emoção, risco zero) somados à detecção determinística de padrões de escrita de IA. Use quando o usuário disser "revisar copy", "melhorar esse texto", "revisão", "está parecendo IA", "polir", "dar uma olhada nesse texto", "feedback de copy", ou logo após qualquer skill copy-* gerar um rascunho. Não reescreve do zero — aprimora preservando a mensagem central.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Systematically review pull requests, feature implementations, and code changes to ensure quality, maintainability, security, and adherence to best practices. Use when reviewing code before merging, conducting peer reviews, performing self-reviews, auditing code quality, checking for security vulnerabilities, ensuring consistent coding standards, verifying test coverage, assessing performance implications, evaluating architectural decisions, or providing constructive feedback to improve team code quality.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
When the user wants to optimize, improve, or increase conversions on any marketing page — including homepage, landing pages, pricing pages, feature pages, or blog posts. Also use when the user says "CRO," "conversion rate optimization," "this page isn't converting," "improve conversions," "why isn't this page working," "my landing page sucks," "nobody's converting," "low conversion rate," "bounce rate is too high," "people leave without signing up," or "this page needs work." Use this even if the user just shares a URL and asks for feedback — they probably want conversion help. For signup/registration flows, see signup-flow-cro. For post-signup activation, see onboarding-cro. For forms outside of signup, see form-cro. For popups/modals, see popup-cro.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.