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

python-quality-and-cli

스타2

포크0

업데이트2026년 4월 24일 16:34

Use when writing or reviewing Python (scripts, services, tests): stdlib CLI patterns, logging, typing, Ruff/Mypy alignment, and safe defaults. Use for cross-org guidance; Engineering owns product code patterns in [PRODUCT_CODE_ROOT]/.

설치

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

Manus에서 실행

출처

MYBENAI-LLC

MYBENAI-LLC/benai-agent-method

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

다운로드

Manus에서 실행

Python quality & CLI (HQ + cross-org)

When to use

HQ agents reference Engineering deliverables or Python examples in [YOUR_PLANS_DIR]/.
Any agent is asked to author, refactor, or critique Python snippets, CLIs, or small tools.
Code review language for handoffs to Engineering (“please align with…”).

Canonical references

[PRODUCT_CODE_ROOT]/docs/engineering/PYTHON_LAW_v1.md (product repo) — locked layers, contracts, scripts, tooling, learn-as-you-go.
shared_context/python_agent_coding_hygiene_v1.md — supplementary habits + external link map.

Engineering: [PRODUCT_CODE_ROOT]/pyproject.toml (Ruff, Mypy) and .cursor/rules/method-python-law.mdc when editing Python in Cursor.

Minimum checklist (before saying “done”)

CLI: argparse (or repo-standard Typer/Click) — working --help, sensible exit codes, early validation.
No secrets in source; use env/config patterns consistent with repo.
pathlib + encoding="utf-8" for text files when applicable.
logging in library/service code; avoid debug print in shared modules.
Tests for new behavior (pytest) when touching [PRODUCT_CODE_ROOT]/ — Engineering executes.
Ruff / Mypy clean per pyproject.toml when changes land in product repo.

Founder links — how to cite them

dl-books → DL book literacy, not coding standard.
GitHub python-ai topic → discover projects; verify against official docs before adopting.
TensorFlow.org → only if TensorFlow is in scope for that task.

Handoff phrase (HQ → Engineering)

Python changes must comply with [PRODUCT_CODE_ROOT]/docs/engineering/PYTHON_LAW_v1.md, [PRODUCT_CODE_ROOT]/pyproject.toml, and shared_context/python_agent_coding_hygiene_v1.md as supplementary.

이 저장소의 다른 Skills

같은 저장소

ai-pipeline

MYBENAI-LLC/benai-agent-method

AI feature engineering — llama, embeddings, RAG quality, inference reliability, cost/token discipline.

2026-04-242

architecture-and-docs

MYBENAI-LLC/benai-agent-method

System architecture, structured code review bar, and technical documentation.

2026-04-242

backend-rag-integration

MYBENAI-LLC/benai-agent-method

Backend HTTP API, SQLite, Qdrant, integration contracts, schema and migration safety.

2026-04-242

benai-code-sections

MYBENAI-LLC/benai-agent-method

Maturity / inspection pass over [ORG_NAME] code sections (BCS). Load your org’s code-sections ledger, run verify ladder, update shared_context summary on main when columns change.

2026-04-242

data-and-ingest

MYBENAI-LLC/benai-agent-method

Data pipelines, ingest, remediation, entity quality — PDF/docs through to vector store.

2026-04-242

decision-ledger-hygiene

MYBENAI-LLC/benai-agent-method

Decision continuity, handoffs, supersession — Engineering Orchestrator (Mike) accountable; pair with session-notes.

2026-04-242

name	python-quality-and-cli
description	Use when writing or reviewing Python (scripts, services, tests): stdlib CLI patterns, logging, typing, Ruff/Mypy alignment, and safe defaults. Use for cross-org guidance; Engineering owns product code patterns in [PRODUCT_CODE_ROOT]/.

Python quality & CLI (HQ + cross-org)

When to use

HQ agents reference Engineering deliverables or Python examples in [YOUR_PLANS_DIR]/.
Any agent is asked to author, refactor, or critique Python snippets, CLIs, or small tools.
Code review language for handoffs to Engineering (“please align with…”).

Canonical references

[PRODUCT_CODE_ROOT]/docs/engineering/PYTHON_LAW_v1.md (product repo) — locked layers, contracts, scripts, tooling, learn-as-you-go.
shared_context/python_agent_coding_hygiene_v1.md — supplementary habits + external link map.

Engineering: [PRODUCT_CODE_ROOT]/pyproject.toml (Ruff, Mypy) and .cursor/rules/method-python-law.mdc when editing Python in Cursor.

Minimum checklist (before saying “done”)

CLI: argparse (or repo-standard Typer/Click) — working --help, sensible exit codes, early validation.
No secrets in source; use env/config patterns consistent with repo.
pathlib + encoding="utf-8" for text files when applicable.
logging in library/service code; avoid debug print in shared modules.
Tests for new behavior (pytest) when touching [PRODUCT_CODE_ROOT]/ — Engineering executes.
Ruff / Mypy clean per pyproject.toml when changes land in product repo.

Founder links — how to cite them

dl-books → DL book literacy, not coding standard.
GitHub python-ai topic → discover projects; verify against official docs before adopting.
TensorFlow.org → only if TensorFlow is in scope for that task.

Handoff phrase (HQ → Engineering)

Python changes must comply with [PRODUCT_CODE_ROOT]/docs/engineering/PYTHON_LAW_v1.md, [PRODUCT_CODE_ROOT]/pyproject.toml, and shared_context/python_agent_coding_hygiene_v1.md as supplementary.