Review code for quality, simplicity, and common mistakes before declaring work complete.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
코딩 규칙, 프레임워크, 리팩터링, 코드 리뷰 (1.7만건)
Review code for quality, simplicity, and common mistakes before declaring work complete.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
chrome-devtools-mcp launcher — a single bash script that resolves Playwright's bundled Chrome-for-Testing and Node.js directly through Nix. See repo README for usage, override mechanisms, and version compatibility.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
odu MCP server launcher — drive CI from a coding agent. `bin/serve` resolves odu via Nix and runs `odu mcp` in the cwd. See the repo README for the tools/resources and override knobs.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Search and explore an Obsidian vault through the NoteBrain CLI (semantic search, tags, backlinks, connections, hidden links, boosted retrieval). Use it whenever the user mentions their notes, knowledge base, Obsidian vault, semantic search, finding connections or unlinked notes, or asks exploratory questions like "what do I know about X", "find notes related to Y", "what connects to Z", or "summarize my notes on W" — even when they never say NoteBrain, vector search, or ChromaDB.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Execute git commits using the Conventional Commits specification. Use this skill whenever the user says "commit", "git commit", "/commit", "stage and commit", "make a commit", "save my changes", or asks to commit specific files or all changes. Also triggers on phrases like "push my changes" (commit first), "commit everything", "commit with message X", or whenever git diff/status suggests uncommitted work the user wants to save. Handles auto-staging, diff analysis, message generation, breaking change detection, batch splitting of unrelated changes, safe pushes, and pre-commit hook failures gracefully. Always use this skill rather than ad-hoc git commit commands.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/spec asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to "review since X".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when you need to resolve an in-progress git merge/rebase conflict.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Interpreter's capabilities with specialized knowledge, workflows, or tool integrations.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Run month-end close for an entity and period, including accrual schedules, balance-sheet roll-forwards, variance commentary, and a controller-ready close package. Use for period-end close work, not daily reconciliation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build a roll-forward schedule for a balance-sheet account or account group, tying beginning balance, activity, reversals, payments, adjustments, and ending balance to GL support. Use for month-end close packages and audit support.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Transcribe audio files locally with Interpreter's builtin-transcribe tool server. Use when a user asks to transcribe speech from recordings without cloud transcription or API keys.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Write flux commentary for P&L and balance-sheet lines over threshold, comparing current period against prior period and budget with drivers explained from underlying activity. Use for month-end close packages and management reporting.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use for AI image, video, audio, or 3D generation/editing. Prefer configured media tools when present, estimate cost before running a paid model, and keep provider credentials in the user's environment or provider configuration.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use for Interpreter app settings and account usage. Prefer the direct workstation tools for reading settings, changing settings, and checking remaining Interpreter balance; use the Interpreter CLI only as a fallback.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create, inspect, and edit Word documents (`.docx`) with local code-execution tools. Use for document drafting, structured edits, tables, comments, and layout-sensitive Word deliverables.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Bootstrap a markdown workspace into a durable wiki structure. Use this when the user wants to initialize a wiki from an empty folder or convert an existing pile of notes into a more structured persistent wiki.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build and maintain a persistent, interlinked markdown wiki (second brain / research notebook / personal knowledge base) from raw sources. Use this skill when the user wants to ingest an article / paper / note / URL / PDF into their wiki, ask a question against their wiki, lint/health-check their wiki, or set up a new wiki from a folder. Triggers include phrases like "add this to my wiki", "ingest this", "file this article", "update my notes with this", "what does my wiki say about X", "health-check my wiki", "find stale/orphan pages", or any workflow involving a `raw/` source folder, `wiki/` markdown folder, `index.md`, or `log.md`. Compatible with Obsidian vaults.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the user explicitly asks for a desktop or system screenshot (full screen, specific app or window, or a pixel region), or when tool-specific capture capabilities are unavailable and an OS-level capture is needed.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Ingest one new source into an existing persistent markdown wiki or established vault workflow. Use this when the user asks to add an article, PDF, note, URL, transcript, or other source into their wiki and wants the source filed, linked, indexed, and logged. If the wiki workflow does not exist yet, use $wiki-bootstrap first. This skill is for the ingest operation only.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Health-check a persistent markdown wiki. Use this when the user wants to find orphan notes, dangling links, missing pages, graph gaps, contradictions to review, or general wiki maintenance opportunities.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Drive a native desktop app through Interpreter's builtin-cua-driver. Use get_app_state, click/type/scroll/drag, and verify by calling get_app_state again when the user asks to operate a real desktop app, browser chrome, native dialog, menu, secure prompt, file chooser, or hidden/background window.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Answer questions against a persistent markdown wiki and optionally file the answer back into the wiki. Use this when the user asks what their wiki says about a topic, wants a comparison across notes, or wants citations grounded in the wiki.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build a period-end accrual schedule by computing each accrual, citing support, and drafting journal entries for controller approval. Use during month-end close; this drafts entries only and must not post them.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use this skill when the user needs advanced Playwright control of an already running browser session through Interpreter's app-managed browser bridge and the `builtin-js-repl` `js_repl` tool, after simple browser page work cannot be handled by the unified `builtin-interpreter` browser page tools.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.