스킬 찾기

Assess and address review feedback on GitHub PRs, GitLab MRs, or in conversation. Use when checking new reviews, responding to comments, rechecking after a push, or following up on approvals and change requests.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when the primary outcome is authoring, rewriting, summarizing, or validating user-facing documentation without implementation comparison or required source attribution, including READMEs, tutorials, API docs, GitLab Markdown, source-faithful summaries, and audience-specific prose.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when the user explicitly asks Rewrite Room to route documentation work, or when audit/sync/freshness, user-facing authoring, citation-driven writing, docs-to-skill conversion, and AI-instruction optimization overlap and exactly one workflow must be chosen.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Reference guide for the Twelve-Factor App methodology — 15 principles (12 original + 3 modern extensions) for building portable, resilient, cloud-native applications. Use when evaluating application architecture, designing cloud-native services, reviewing codebases for methodology compliance, advising on configuration, scaling, observability, security, and deployment patterns. Incorporates the 2025 open-source community evolution and cloud-native reinterpretations of each factor.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Single-pass SOLID review — dispatches one reviewer over the complete ruleset, emitting the fixed candidate schema.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Enforce mandatory pre-action verification checkpoints to prevent pattern-matching from overriding explicit reasoning. Use this skill when about to execute implementation actions (Bash, Write, Edit) to verify hypothesis-action alignment. Blocks execution when hypothesis unverified or action targets different system than hypothesis identified. Critical for preventing cognitive dissonance where correct diagnosis leads to wrong implementation.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Relay agent results without corrupting exact counts, failure reasons, source scope or status. Use when receiving agent output or handing results to another actor; distinguish observations from attributed conclusions and reference complete artifacts.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Integrate multiple source findings into an attributed synthesis or comparison. Use for combine these summaries, synthesize results, merge findings or multi-source analysis. Preserve claim-level provenance, coverage, qualifiers, conflicts and uncertainty rather than repeatedly compressing narrative summaries.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Applies and teaches Python 3.11+ modernization patterns with PEP citations. Use when reviewing or writing Python code to apply built-in generics (PEP 585), pipe unions (PEP 604), walrus operator (PEP 572), match-case (PEP 634), Self type (PEP 673), exception notes (PEP 678), StrEnum, tomllib, pytest-mock fixtures, Typer Annotated syntax, or Rich terminal output — or when refactoring legacy typing imports or elif chains to modern equivalents.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use before any CLI/TUI display code is written, modified, or audited — runs the 7-stage discipline (Context, Register, Shape brief, Implement, Critique, Audit, Polish) for Typer, Rich, Textual, and Questionary work, grounded in per-project PRODUCT.md and DESIGN.TUI.md/DESIGN.md. Triggers on output formatting, display design, interactive prompts, visual consistency, TUI layout, progress display, dashboard design, design audit, design polish, design critique, shape brief, register decision (brand-cli vs product-cli), and AI-slop checks.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when diagnosing a Python traceback, failing test, intermittent failure, integration defect, or other unexpected runtime behavior.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when creating a new feature development task — scaffolds a structured task file at .claude/tasks/{feature-name}.md with phased breakdown (Design, Implementation, Testing, Documentation), acceptance criteria, context preservation, and TaskCreate tracking. Activates on "create a feature task", "set up development tracking", "plan a feature implementation", or when preparing work for python-cli-architect or python-pytest-architect agents.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when independently assessing how bounded Python code could accomplish the same behavior with less maintained code, more Pythonic design, newer language/stdlib capabilities, or well-maintained ecosystem libraries.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Specialist skill for Python data engineering — pandas, polars, DuckDB, numpy, ETL pipelines, tabular data ingestion, and notebook-to-module extraction. Use when working with dataframes, data validation at ingress boundaries, merge/join operations, typed column contracts, or choosing between pandas vs polars vs DuckDB for a data task.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when writing Python scripts that must run on Windows, Linux, and macOS — especially when Rich or Typer output breaks on Windows, when dealing with Unicode/encoding errors, ANSI escape handling, terminal detection, path separators, or console color support. Provides verified cross-platform patterns covering stdout/stderr encoding guards, Windows console quirks, terminal capability detection, and portable I/O for CLI, TUI (Rich/Textual), and GUI environments.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when the user asks for a read-only, actionable audit of Python code quality, modernization, maintenance burden, ecosystem opportunities, or Pythonic design across a PR, git diff, staged/unstaged changes, files, or directories.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when working with ruff — this skill's ruff policy and required overrides to Astral's official guidance. Pair with `astral:ruff` (if installed) for general usage.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when a Python task explicitly requires test-driven development, tests-first implementation, or a red-green-refactor workflow.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when building CLI applications with Typer and Rich — creating commands with Annotated parameter syntax, defining arguments and options, composing subcommands, async concurrent CLI tasks with semaphores, testing with CliRunner, PEP 723 shebang scripts, progress bars, Rich terminal output, or non-TTY display width handling.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when building dependency-free Python 3.11+ scripts for airgapped, stdlib-only, or restricted environments where third-party package installation is prohibited — triggers on "stdlib-only", "airgapped", "no dependencies", "no internet", "restricted environment", or confirmed environments where external packages cannot be installed.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when implementing a Python feature, adding CLI commands, writing pytest suites, reviewing Python code, debugging, or refactoring. The primary Python engineering workflow orchestrator — classifies the task and delegates through this plugin's own specialist agents (architect → implement → test → review), sized to the task. Delegates to python-cli-architect (implementation), python-pytest-architect (tests), code-reviewer (review), python-cli-design-spec (architecture). Triggers on any Python task requiring specialist agent coordination or multi-agent execution.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Provides Hatchling build backend guidance for Python packaging — use when configuring pyproject.toml metadata, build targets (wheel, sdist, binary), file selection with git-style globs, build hooks, metadata hooks, version management (code/regex/env sources), editable installs, the hatch-vcs plugin, plugin development, build environment setup (UV/pip/Cython), setuptools migration, or troubleshooting Hatchling errors. Covers PEP 517/518/621/660 standards and context variable interpolation.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Runs deterministic Python quality checks against a path or scope — formatting, linting, type checking, and typing-boundary policy. Use when checking or fixing code quality via prek, ruff, ty, pytest, or the check-typing-boundaries policy script. Reports results grouped by category; fixes only when explicitly requested.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Provides agent selection criteria, workflow patterns (TDD, feature addition, code review, refactoring, debugging), quality gates, and python-cli-architect vs stdlib-scripting routing for Python engineering tasks. Activated by python-engineering:orchestrate at Step 1 before any task is routed. Also activates when an orchestrator needs to select the correct Python specialist agent or chain agents across a multi-step Python workflow.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.