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

acp-python-style

스타7

포크0

업데이트2026년 2월 14일 03:44

Apply the formatting and structural conventions used in mugen/core/plugin/acp. Use when creating or modifying Python modules in ACP, or nearby plugin/test code that should match ACP style (for example mugen/core/plugin/audit and ACP-focused tests).

설치

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

Manus에서 실행

출처

vorsocom

vorsocom/mugen

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

다운로드

Manus에서 실행

ACP Python Style

Overview

Match ACP formatting by copying the nearest ACP peer-file shape, then validate with this skill's checker before finalizing edits.

Workflow

Choose a local ACP exemplar in the same layer before editing.
Mirror the exemplar's file scaffold: module docstring, optional __all__, import grouping, class/function layout, and multiline formatting.
Apply the concrete rules in references/acp_style_guide.md.
Run the style checker on changed files.
Fix reported style issues before returning final output.

Validation Command

Run from repository root:

python .codex/skills/acp-python-style/scripts/check_acp_style.py <changed_file.py> [more_files.py]

The checker auto-detects max line length from .vscode/settings.json (Black args or rulers). Use --max-line-length to override when needed.

To scan ACP as a whole:

python .codex/skills/acp-python-style/scripts/check_acp_style.py

Operating Rules

Prefer matching nearby ACP files over generic formatter output.
Keep edits surgical; do not reformat unrelated files.
Keep line length at the workspace formatter limit. Current repo config in .vscode/settings.json is Black --line-length 88.
Use double-quoted strings to match ACP's prevailing style.
Resolve model forward references for static analysis: Prefer TYPE_CHECKING imports for unsuppressed Mapped["TypeName"] annotations. Use inline # type: ignore only when a type-only import is not practical.
Keep pylint pragmas in ACP format when needed (one directive per line).
Re-run the checker after every non-trivial edit.

References

Style source of truth: references/acp_style_guide.md
Automated checker: scripts/check_acp_style.py

이 저장소의 다른 Skills

같은 저장소

alembic-migration-checker

vorsocom/mugen

Assess Alembic migration correctness and consistency in mugen. Use when reviewing migration quality before running migrations, or when debugging migration failures. Runs revision graph checks, static revision checks, offline SQL generation, duplicate CREATE TYPE detection, and optional disposable Postgres upgrade/downgrade roundtrip.

2026-03-167

acp-http-e2e-tester

vorsocom/mugen

Run repeatable ACP plugin HTTP end-to-end checks in mugen using Hypercorn and curl. Use when validating a new or changed ACP-based plugin resource/action surface, reproducing API behavior regressions, or confirming expected HTTP status/body behavior for tenant-scoped CRUD and `$action` transitions.

2026-03-027

prepush-quality-gates

vorsocom/mugen

Run mugen pre-push quality gates end-to-end. Use when you need a single repeatable check before commit/push that confirms full unit tests pass, full E2E template validations pass, and total coverage remains at 100%.

2026-03-027

name	acp-python-style
description	Apply the formatting and structural conventions used in mugen/core/plugin/acp. Use when creating or modifying Python modules in ACP, or nearby plugin/test code that should match ACP style (for example mugen/core/plugin/audit and ACP-focused tests).

ACP Python Style

Overview

Match ACP formatting by copying the nearest ACP peer-file shape, then validate with this skill's checker before finalizing edits.

Workflow

Choose a local ACP exemplar in the same layer before editing.
Mirror the exemplar's file scaffold: module docstring, optional __all__, import grouping, class/function layout, and multiline formatting.
Apply the concrete rules in references/acp_style_guide.md.
Run the style checker on changed files.
Fix reported style issues before returning final output.

Validation Command

Run from repository root:

python .codex/skills/acp-python-style/scripts/check_acp_style.py <changed_file.py> [more_files.py]

The checker auto-detects max line length from .vscode/settings.json (Black args or rulers). Use --max-line-length to override when needed.

To scan ACP as a whole:

python .codex/skills/acp-python-style/scripts/check_acp_style.py

Operating Rules

Prefer matching nearby ACP files over generic formatter output.
Keep edits surgical; do not reformat unrelated files.
Keep line length at the workspace formatter limit. Current repo config in .vscode/settings.json is Black --line-length 88.
Use double-quoted strings to match ACP's prevailing style.
Resolve model forward references for static analysis: Prefer TYPE_CHECKING imports for unsuppressed Mapped["TypeName"] annotations. Use inline # type: ignore only when a type-only import is not practical.
Keep pylint pragmas in ACP format when needed (one directive per line).
Re-run the checker after every non-trivial edit.

References

Style source of truth: references/acp_style_guide.md
Automated checker: scripts/check_acp_style.py