941건 · 관련도순
Manage JIRA collaboration surface via the jira-as wrapper: comments, attachments, watchers, notify. Triggers: 'comment on KEY', 'add attachment to KEY', 'watch KEY', 'notify KEY watchers'. Internal-vs-public comment safety enforced. NOT for issue CRUD (mk:jira-issue); NOT for issue links (mk:jira-relationships).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
JIRA issue CRUD via the jira-as wrapper. Triggers: 'create bug/task/story', 'show me PROJ-123', 'get/view/look up issue', 'update PROJ-123', 'delete PROJ-123'. NOT for transitions (mk:jira-lifecycle); NOT for comments/attachments (mk:jira-collaborate); NOT for bulk ops (mk:jira-bulk); NOT for issue links (mk:jira-relationships); NOT for time logging (mk:jira-time); NOT for sprint/epic (mk:jira-agile).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Enforces KISS/DRY/YAGNI during authoring and ad-hoc quality reviews. Pragmatic standards: concise, direct, no unnecessary comments. NOT for post-hoc diff/PR review (see mk:review); NOT for behavior-preserving simplification passes (see mk:simplify).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Confluence page CRUD via the confluence-as wrapper. Triggers: 'create page in SPACE', 'show me page 12345', 'update title of page 12345', 'delete page 12345', 'page hierarchy under 12345', 'copy page 12345 to SPACE'. NOT for bulk ops on 10+ pages (mk:confluence-bulk); NOT for spec analysis (mk:confluence-spec-analyst); NOT for comments/attachments/labels (mk:confluence-collaborate).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Manage Confluence collaboration surface via the confluence-as wrapper: comments, attachments, labels, watchers. Triggers: 'add comment to page 12345', 'upload attachment to page 12345', 'label page 12345 as urgent', 'watch page 12345'. Inline-vs-footer comment safety enforced. NOT for page CRUD (mk:confluence-page); NOT for bulk ops (mk:confluence-bulk).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
DraftForge PR lifecycle workflow. Use when the user runs /pr, opens or pushes a pull request, or asks to monitor CI checks and Copilot review on a branch. Creates the PR (or reuses an existing one), polls GitHub Actions and Copilot up to ~15 min, then analyses CI failures and Copilot comments and reports findings grouped by file and skill.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
コード・テストコード・コミットログ・コードコメントのどこに何を書くかを決めるときに使う。コードには How、テストコードには What、コミットログには Why、コードコメントには Why not を書き分ける。実装時とコミット・PR 作成時に使う。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Do market research, user research, and product validation on Reddit with semantic search across 50K+ subreddits, 20M+ posts, and 40M+ comments via reddapi.dev - search by meaning, not keywords, no Reddit OAuth or app registration needed. Use when the user wants to research what people say on Reddit, find user pain points and complaints, validate a product or niche idea, do competitor and market research, track subreddit trends over a date range, or discover which subreddits discuss a topic. Also use when the user mentions 'Reddit research', 'Reddit 调研', 'search Reddit', 'subreddit discovery', 'niche validation', 'pain points', 'user complaints', or 'Reddit trends'. Requires REDDAPI_API_KEY. For B2B lead scoring, see reddit-leads; for a bare API reference, see reddit-search-api.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Review a small code or documentation change and return only evidence-backed correctness findings. Use in the Codex How To local plugin lab; do not modify files or post remote comments.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Review PRs: diffs, inline comments via gh or REST.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
How to write JSDoc on @rhinestone/sdk public symbols, which is autogenerated into the published SDK Reference. Use when adding or editing doc comments on entry points, the account instance, actions, or utils in sdk/src.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Ultra-compressed code review comments. Cuts noise from PR feedback while preserving the actionable signal. Each comment is one line: location, problem, fix. Use when user says "review this PR", "code review", "review the diff", "/review", or invokes /caveman-review. Auto-triggers when reviewing pull requests.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Fetch and display the full status of the current PR — CI checks, GitHub Actions runs, reviews, and code comments — using GitHub MCP tools. Invoke manually with /pr-status.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the user asks for QA analysis, test planning, test cases, or root-cause analysis of a defect. Also use for post-merge PR review analysis: auditing recent closed PRs for Devin/GitHub/security bot comments, verifying whether requested corrections were applied, and turning pending fixes into SPECs.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
学术论文审稿意见回复信。输入是审稿人意见全文、reviewer comments、major/minor revision letter、或既有的 rebuttal 草稿时使用。功能包括：意见拆解 + ID 分配 + 行动映射（classify）、起草 point-by-point 回复（draft）、润色既有草稿（polish）、防御性与真实性审查（audit）、起草给编辑的 cover letter（cover）。覆盖期刊与会议 rebuttal、4 种困难场景（矛盾意见、不可能实验、缺关键证据、minor revision）。不适用于：正文段落写作（用 academic-writing）、图表生成（用 academic-figure）、参考文献格式（用 academic-citation）。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Summarize the current pull request including diff, comments, and review status. Use when reviewing a PR, preparing for a review meeting, or getting a quick PR overview.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Interactive pair review of a PR. Fetches the diff, scouts for context, then walks through each changed file one at a time. Collects review comments in a bag with conventional comment prefixes, previews them, and posts only after explicit approval. Trigger on: pair review, let's review together, walk me through the PR, review with me.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
When processing code review feedback (bot or human) before changing anything — triages, verifies and pushes back with technical reasoning — even when the user just says 'fix the comments'.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Morning startup workflow for daily notes, yesterday summary, agenda, status comments, meeting sections, and daily branch setup. Use when invoked as `$work-start-day` or when the user asks to start the work day.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
End-of-day — draft and post daily comments for tracked tickets missing a comment
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Address GitHub PR review comments at line, file, and PR level by fetching, evaluating, fixing, committing, and resolving feedback. Use when invoked as `$pr-resolve-review-feedback` or when the user asks to resolve PR feedback.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Post findings from the most recent review output as inline GitHub PR comments and record them in today's daily note. Use when invoked as `$pr-post-review-findings` or when the user asks to post review findings to the current PR.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Address GitHub PR review feedback at line, file, and PR level — fetch, evaluate, fix, commit, and resolve. Use when given a PR URL, a review-comment URL, or a PR-level comment URL. Triggers: GitHub discussion URLs, "fix this review comment", "address PR feedback", "resolve PR comments", PR URLs with #discussion_, #issuecomment-, or #pullrequestreview- fragments.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Comprehensive code review using specialized agents — orchestrates code, comments, tests, errors, types, and simplify agents sequentially.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.