212건 · 관련도순
Review someone else's PR through an architectural/strategic lens — does it shift design, raise complexity, or quietly change precedent? Drives a brief reflective discussion with the user, then posts a concise review comment via `gh`. Defers line-level and bug-hunting concerns to AI review bots and the PR author.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create a pull request from the current branch. Triggers on create PR/open PR/make PR/submit PR/push PR/raise PR/open a pull request/create a pull request/ready to merge/branch is ready when the user wants to turn their current branch into a GitHub pull request with a well-structured description
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the user asks to "monitor brand mentions", "set up social listening", "did anything spike about us this week", or "watch these accounts for buying triggers"; runs always-on keyless listening — a versioned listening-query architecture (brand variants incl. misspellings and 中文 names, exclusion terms, per-source syntax for HN Algolia / Bluesky / GDELT / Tavily), a mention sweep with six-class triage (crisis / bug / lead / praise / question / spam) each routed with an SLA, a 7-day rolling baseline with spike flags (the crisis trigger input), a B2B trigger watchlist (funding / hiring / launch signals), and an explicit coverage disclosure where X/IG/TikTok/LinkedIn/小红书 numbers are proxy-labeled, never Measured. Not for launch-window telemetry (T-0→T+30 rank and review polling) — use launch-monitor. 舆情监听/品牌提及监测/基线突刺/触发信号
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the user asks to "triage our comments, DMs, and mentions", "draft replies to this thread", "can we repost this fan post", or "set up inbox SLAs and an escalation path"; produces a ranked triage queue with register detection (sincere / ironic / performative / parasocial, sentiment-inversion table included — "this is so bad" under a comedy register is praise), a commenter taxonomy (troll monitor-only / rager / misguided / unhappy-customer / advocate) with a response-tier ladder and per-channel SLAs, an escalation matrix ending at the crisis path, a moderation ladder plus house rules for owned spaces, and a UGC curation-and-rights mode whose dated permission entries route to the channel registry — every reply is a ranked DRAFT a human posts; nothing is ever auto-sent. Not for launch-window feedback triage — use launch-feedback-synthesizer. 评论私信提及分诊/语域识别/回复草稿/UGC授权
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create a pull request from the current branch for pitwall, into the right base for this repo's two-tier flow — feature branches (`dev-<feature>`) target `dev`, and `dev` itself targets `master` as a release PR. Analyzes the new commits, drafts a PR title and a Summary/Test-plan body matching this repo's existing PR style, previews it for approval, then creates it via the `gh` CLI. A release PR into `master` additionally settles the version and writes the release notes file before the tag exists. Use whenever the user says "pr", "pull request", "open a pr", "create pr", "ship it", "merge into dev", "merge into master", "cut a release", "raise a pr", or anything about getting the current branch merged — even if they don't say the word "skill".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Orchestrate any tdmcp test-coverage work: run the coverage harness, inspect coverage gaps, plan focused Vitest/msw or bridge tests, delegate coverage writers, verify coverage deltas, and re-run gates. Use whenever the user asks to raise coverage, add broad regression coverage, create a test harness, improve tests, re-run a coverage wave, or fix a coverage gate.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Write focused tdmcp tests for one assigned coverage gap. Use for Vitest/msw unit tests, integration tests, bridge tests, CLI/config/resource tests, and regression tests that should raise coverage without weakening behavior.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when: reviewing or producing any external-facing prose — ADRs, proposals, GitHub comments, Telegram messages, cover letters, client drafts, or planner-mode wording. Removes AI-tell patterns and raises writing quality before output leaves the team.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Focused Signals scout for PostHog projects running surveys. Watches active surveys for score regressions (NPS / CSAT / rating drops), response-volume drops, abandonment spikes, and targeting drift, AND aggregates open-text responses into recurring themes the team should know about (clusters of complaints, praise, feature requests). Emits findings only when a theme or anomaly clears the confidence bar; otherwise writes durable memory and closes out empty. Self-contained peer in the signals-scout-* fleet — no dependencies on other skills.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Extract appraised value, property details, and comparable sales from a property appraisal report into structured JSON.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Change what something MEANS before you change what it IS — Rory Sutherland's cheapest lever. Use when a product, price, feature, or message is objectively fine but feels cheap, generic, boring, overpriced, or unjustified; when the user says 'how do we make this feel more premium/valuable/exciting', 'people don't get why it's worth it', 'how do we reposition/rename/repackage this', or wants to raise perceived value without changing the product or cutting the price. Covers renaming, recategorising, mental accounting (price framing), creating artificial value, and context-shifting. Inspired by Rory Sutherland's *Alchemy*. Routed to from psycho-logic. 日本語の相談（「高いと言われる」「安っぽく見える」「値下げせずに高級感を出したい」）にも使う。中文咨询（“被说太贵”“显得廉价”“不降价也想显得高级”）也适用。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Prepare a request to change the terms of a Japanese job offer before accepting it, sorting what the user wants changed (pay components, start date, work style, location, title, probation) by priority, tying each ask to a basis the user can show (the written offer, the job posting, what was said in interviews, their own records), working the timing back from the acceptance deadline, and drafting the message to the employer or recruiting agent. Use when a user has an offer and wants to ask for higher pay, a later start date, more remote days, or other changed terms, or wants to know how to raise it without losing the offer; do not use to predict whether the request will succeed, to set a target figure from market rates, to fabricate a competing offer, to decide whether to accept, or to send anything to the employer.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Decides whether and how to polish a draft genome assembly to raise consensus accuracy (QV) with read-type-matched tools - Racon and medaka (ONT consensus), dorado polish, Polypolish and pypolca (Illumina, repeat-aware), Pilon (legacy short-read), NextPolish/NextPolish2, Hapo-G (haplotype-aware), ntEdit, and DeepPolisher/PEPPER-Margin-DeepVariant for human. Covers the do-not-polish-HiFi rule, the medaka basecaller-model footgun, held-out Merqury QV as the only honest stop signal, and the haplotype-collapse trap. Use when correcting homopolymer indels or residual SNPs in a long-read assembly, deciding if a HiFi assembly needs polishing, or choosing an ONT vs hybrid vs short-read polishing chain.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Weekly engineering retrospective. Analyzes commit history, work patterns, and code quality metrics with persistent history and trend tracking. Team-aware with per-person contributions, praise, and growth areas. Use when asked for weekly retro, what shipped this week, or engineering retrospective.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Weekly engineering retrospective. Analyzes commit history, work patterns, and code quality metrics with persistent history and trend tracking. Team-aware: breaks down per-person contributions with praise and growth areas. Use when asked to "weekly retro", "what did we ship", or "engineering retrospective". Proactively suggest at the end of a work week or sprint. (gstack)
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create branch, atomic commits, push, and open a pull request with terse, exact messages. Conventional branch + commit format. PR title ≤70 chars, body says "why", not "what". Use when the user says "create pr", "create pullrequest", "create pull request", "make pr", "open pr", "open pullrequest", "open pull request", "submit pr", "raise pr", "/create-pr", or asks to ship/send changes as a pull request (PR/pullrequest/pull-request, any spelling).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Decides whether and how to polish a draft genome assembly to raise consensus accuracy (QV) with read-type-matched tools - Racon and medaka (ONT consensus), dorado polish, Polypolish and pypolca (Illumina, repeat-aware), Pilon (legacy short-read), NextPolish/NextPolish2, Hapo-G (haplotype-aware), ntEdit, and DeepPolisher/PEPPER-Margin-DeepVariant for human. Covers the do-not-polish-HiFi rule, the medaka basecaller-model footgun, held-out Merqury QV as the only honest stop signal, and the haplotype-collapse trap. Use when correcting homopolymer indels or residual SNPs in a long-read assembly, deciding if a HiFi assembly needs polishing, or choosing an ONT vs hybrid vs short-read polishing chain.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Offers, compensation framing, and negotiation planning. Use when evaluating offers or raises.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Pricing strategy for technical products. Use when choosing usage-based vs seat-based, designing freemium thresholds, structuring enterprise pricing conversations, deciding when to raise prices, or using price as a positioning signal.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.