원클릭으로 Manus에서 모든 스킬 실행

code-review

스타0

포크0

업데이트2026년 6월 4일 12:36

Use this skill when the user wants a production-grade review of Python code, a Python pull request, or a Python-focused diff. Check architecture, security, code quality, tests, documentation, deployment risk, and code-documentation consistency. Trigger on requests like "review this Python PR", "audit this diff", "check code quality", or "give me a fix plan". Do NOT use it for non-Python code review, writing new features, dependency-only changes, pytest-suite-specific audits where `pytest-suite-review` is a better fit, or iterative review-fix-rerun loops where `code-review-loop` is a better fit.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

argythana

argythana/python-ml-skills

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Python Code Review

Systematic code review with actionable feedback organized by severity.

Process

Gather context

git diff --name-only main
git diff main
git log main..HEAD --oneline

Run automated checks

ruff check --output-format=json <files>
vulture --min-confidence=80 <files>
mypy <files>

Apply review checklists - see references below
Generate report with issues and fix plan

Severity Levels

Level	Definition	Action
Critical	Security flaws, data loss, breaking changes	Blocks merge
High	Resource leaks, wrong layer, N+1 queries	Fix before merge
Moderate	Missing tests, complexity >10, swallowed exceptions	Should address
Low	Style beyond linter, minor refactoring	Optional

Review Categories

Apply these checklists to changed files:

Architecture - Layer violations, dependency direction, god classes
- See references/architecture.md
Security - Injection, secrets, path traversal, deserialization
- See references/security.md
Quality - Complexity, error handling, performance
- See references/quality.md
Testing - Coverage, assertions, isolation, fixtures
- See references/testing.md
Documentation - Docstrings, README accuracy
- See references/documentation.md
Deployment - Dockerfile, Helm, migrations
- See references/deployment.md
Consistency - Code-docs sync, signature matches
- See references/consistency.md

Output Format

# Code Review Report

**Status**: PASS | NEEDS_WORK | BLOCKED

## Issues
| Severity | Count |
|----------|-------|
| Critical | N |

### [Category]
- [severity] file:line - description
  - Fix: specific suggestion

## Fix Plan
1. [Issue] - [Action]

Principles

Be specific: "Add try/except at line 42" not "improve error handling"
Verify first: Check functions exist before suggesting them
Focus on changes: Don't refactor untouched code
Provide working examples

이 저장소의 다른 Skills

같은 저장소

code-review-loop

argythana/python-ml-skills

Use this skill when the user wants an iterative `code-review` loop over Python changes: review a Python diff, PR, branch, or commit range with `code-review`, fix the actionable Critical, High, and Moderate findings, run the relevant checks and tests, and repeat until 5 consecutive clean PASS reviews, `insufficient evidence`, or max cycles. Trigger on "run code-review until clean", "keep reviewing and fixing this Python PR until it passes", or "fix the code-review findings and rerun review until acceptable". If the target repo, diff, branch, commit, or commit range is referenced but unavailable, ask after routing. Do NOT use for a single review-only pass; use `code-review`. Do NOT use for pytest-suite-specific audit loops; use `pytest-suite-review-loop`. Do NOT use for implementing a task against Acceptance Criteria; use `task-implementation-loop`. Do NOT use for non-Python code, dependency-only changes, or writing new features from scratch.

2026-06-040

obsidian-create-note

argythana/python-ml-skills

Use when the user wants to import a local Markdown file as a new note into a personal Obsidian vault — prompts like "import this .md into Obsidian", "add this Markdown doc to my vault", or "create a note from this file". The vault root is discovered at runtime: `OBSIDIAN_VAULT` env var if set, otherwise the single directory under `$HOME/Documents` (depth 3) containing `.obsidian/`. If the source Markdown path is missing, ask for it. Do NOT use for: editing, renaming, moving, or deleting existing notes; vault-wide search; daily notes (`daily/`); Literature notes (`Literature/`); ephemeral scratch (`ephemeral/`); Excalidraw drawings; fetching from a URL (use `url-reader` first); or authoring note content from scratch. Do NOT run `git` — the `obsidian-git` plugin owns commits. Assumes the layout in `references/vault-conventions.md` (`all_notes/`, `tags/`, etc.).

2026-05-250

tutorial-expand

argythana/python-ml-skills

Use when expanding, annotating, rewriting, or drafting a section or whole notebook of an official tutorial for a Python data/ML library (e.g. scikit-learn, PyTorch, pandas, matplotlib, NumPy, SciPy, Plotly) so it is friendlier for beginner data scientists and CS students. Trigger on prompts like "expand this scikit-learn section", "explain this pandas concept better", "make this PyTorch notebook beginner-friendly", or "why does this feature exist". If the target notebook or cell is unclear, ask after routing. Do NOT use for general Python tutorial writing unrelated to data/ML libraries (Django, Flask, application code), editing the upstream library itself, non-tutorial docs (`README.md`, `CLAUDE.md`), or non-teaching notebook changes (file moves, dependency bumps, formatting, kernel metadata). If a library-specific tutorial-expand skill is installed (e.g. `mlflow-tutorial-expand`), prefer that. For deps use `uv-deps`; for staging use `git-staging`; for messages use `commit-message`.

2026-05-250

lazy-imports

argythana/python-ml-skills

Use this skill when the user wants to lazily import Python modules, defer module loading until first use, or reduce Python or CLI startup cost by changing import behavior. Trigger on requests like "import X lazily", "don't load pandas until it's used", "use PEP 810", "use `wrapt.lazy_import()`", or "make this CLI's imports lazy". If the target code or supported Python version is missing and cannot be inferred from the repo, ask for it after routing. Do NOT use it just because a Python file has heavy dependencies, or for general import cleanup, generic startup tuning that is not about imports, or dependency-management requests where the main task is adding or updating packages; use `uv-deps` for that work.

2026-05-200

uv-deps

argythana/python-ml-skills

Use when the task is to manage dependencies in a `uv` project — either a single-package project (one `pyproject.toml`) or a `uv` workspace monorepo (multiple per-package `pyproject.toml` files plus a root `uv.lock`). Covers add, remove, update, sync, lock, build, export, or reorganize packages, dependency groups, extras, and workspace sources via `uv` commands rather than hand-editing `pyproject.toml`. Trigger for requests like 'add a package', 'uv sync', 'move this to dev dependencies', 'update uv deps', 'remove X from package Y', 'regenerate constraints.txt', or 'build a wheel'. Do NOT use for Poetry/pip/conda/pip-tools workflows, manual virtualenv setup or activation, import sorting, or unrelated `pyproject.toml` edits such as project metadata or build config.

2026-05-200

do-literature-review

argythana/python-ml-skills

Use this skill when the user asks for a verifiable literature review or peer-reviewed citations for an ADR, design doc, paper, or technical decision, with prompts like "literature review on X", "find papers on X", "survey the literature on X", or "cite peer-reviewed sources for X". Enforce structural verification: every emitted citation needs metadata lookup, full-text retrieval, a supporting quote with locator, byte-for-byte author attribution, Negative Findings, and a self-audit table. Do NOT use it for single-URL summarization, drafting the surrounding ADR, casual citation pointers where verification is explicitly waived, fictional references, or unsourced factual questions.

2026-05-060

name

code-review

description

Python Code Review

Systematic code review with actionable feedback organized by severity.

Process

Gather context

git diff --name-only main
git diff main
git log main..HEAD --oneline

Run automated checks

ruff check --output-format=json <files>
vulture --min-confidence=80 <files>
mypy <files>

Apply review checklists - see references below
Generate report with issues and fix plan

Severity Levels

Level	Definition	Action
Critical	Security flaws, data loss, breaking changes	Blocks merge
High	Resource leaks, wrong layer, N+1 queries	Fix before merge
Moderate	Missing tests, complexity >10, swallowed exceptions	Should address
Low	Style beyond linter, minor refactoring	Optional

Review Categories

Apply these checklists to changed files:

Architecture - Layer violations, dependency direction, god classes
- See references/architecture.md
Security - Injection, secrets, path traversal, deserialization
- See references/security.md
Quality - Complexity, error handling, performance
- See references/quality.md
Testing - Coverage, assertions, isolation, fixtures
- See references/testing.md
Documentation - Docstrings, README accuracy
- See references/documentation.md
Deployment - Dockerfile, Helm, migrations
- See references/deployment.md
Consistency - Code-docs sync, signature matches
- See references/consistency.md

Output Format

# Code Review Report

**Status**: PASS | NEEDS_WORK | BLOCKED

## Issues
| Severity | Count |
|----------|-------|
| Critical | N |

### [Category]
- [severity] file:line - description
  - Fix: specific suggestion

## Fix Plan
1. [Issue] - [Action]

Principles

Be specific: "Add try/except at line 42" not "improve error handling"
Verify first: Check functions exist before suggesting them
Focus on changes: Don't refactor untouched code
Provide working examples