ワンクリックでManusで任意のスキルを実行

cli-tooling-maintainer

スター1

フォーク0

更新日2026年4月2日 18:35

Maintain SoulMap AI command-line tooling so Python entry points, shell wrappers, stdin payload handling, and local automation scripts stay consistent.

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

tuanductran

tuanductran/soulmap-ai

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

CLI tooling maintainer

Use this skill when changing repo tooling exposed through python -m ..., shell scripts under scripts/, or stdin-driven helpers in src/soulmap/runtime/.

Do not use this skill for

GitHub Actions workflow design, use github-actions-maintainer
packaging artifact review, use packaging-maintainer
general Python refactors with no CLI or tooling surface, use code-quality-review

Mission

Keep the repo's command-line surfaces predictable, documented, and cross-platform enough for local development workflows.

Sources to check first

../rules/python-tooling.md
../rules/repo-workflow.md
docs/engineering/DEV.md
scripts/
src/soulmap/devtools/
src/soulmap/runtime/io/cli_payload.py

What to look for

stale command examples or old invocation styles
shell wrappers that duplicate Python entry-point behavior
inconsistent stdin payload parsing across tooling modules
missing or misleading docs for CLI behavior
exit-code or stderr behavior that would confuse automation

Workflow

Identify the Python entry point or shell wrapper being changed.
Compare it with nearby scripts, docs, and tests so command behavior stays aligned.
Prefer shared payload parsing and JSON error helpers where the contract matches.
Keep shell wrappers thin when Python already owns the logic.
Update docs or smoke tests if the command surface changes.
Run the relevant repo checks.

Expected output

Findings

List mismatches in command behavior, docs, or wrapper layers.

Fixes

Summarize what was simplified or synchronized.

Validation

State the commands or tests you ran.

Definition of done

The tooling surface should be:

consistent across Python, shell, and docs
easy to invoke with current repo commands
free of needless wrapper duplication
covered by the right smoke or regression checks

このリポジトリの他の Skills

同じリポジトリ

soulmap-ai

tuanductran/soulmap-ai

SoulMap, a reflective companion that helps people stop abandoning themselves. Includes a central coordination layer, a clear response pipeline, routing guidance, depth calibration, epistemic guardrails, safety guardrails, voice system, brand doctrine, and reusable templates. Mirror, not guide.

2026-07-181

detector-engineer

tuanductran/soulmap-ai

Build and maintain Python detector modules that identify framework selection signals in conversation history.

2026-07-171

frameworks

tuanductran/soulmap-ai

SoulMap reflective response frameworks covering emotional de-escalation, grief, existential reflection, inner parts, life direction, shadow work, synthesis, and relational inquiry. Relevant for tasks that require choosing or applying the core reflective method for a user conversation.

2026-07-161

safety

tuanductran/soulmap-ai

SoulMap safety and boundary rules covering crisis handling, dependency prevention, trauma-informed language, prompt injection defense, and scope control. Relevant for requests that involve harm, escalation, refusal, redirection, or questions about what SoulMap must not do.

2026-07-161

spiritual

tuanductran/soulmap-ai

SoulMap symbolic spiritual materials covering brand-safe numerology, chakra policy, healing metaphors, and archetypal language. Relevant for tasks that involve spiritual framing within SoulMap's grounded, non-predictive, non-grandiose boundaries.

2026-07-161

brand

tuanductran/soulmap-ai

SoulMap brand doctrine, positioning, message hierarchy, surface-specific rules, and strategic direction. Relevant for tasks that concern what SoulMap is, what it is not, how it sounds in public, or how brand language stays aligned across product surfaces.

2026-07-051

name	cli-tooling-maintainer
description	Maintain SoulMap AI command-line tooling so Python entry points, shell wrappers, stdin payload handling, and local automation scripts stay consistent.

CLI tooling maintainer

Use this skill when changing repo tooling exposed through python -m ..., shell scripts under scripts/, or stdin-driven helpers in src/soulmap/runtime/.

Do not use this skill for

GitHub Actions workflow design, use github-actions-maintainer
packaging artifact review, use packaging-maintainer
general Python refactors with no CLI or tooling surface, use code-quality-review

Mission

Keep the repo's command-line surfaces predictable, documented, and cross-platform enough for local development workflows.

Sources to check first

../rules/python-tooling.md
../rules/repo-workflow.md
docs/engineering/DEV.md
scripts/
src/soulmap/devtools/
src/soulmap/runtime/io/cli_payload.py

What to look for

stale command examples or old invocation styles
shell wrappers that duplicate Python entry-point behavior
inconsistent stdin payload parsing across tooling modules
missing or misleading docs for CLI behavior
exit-code or stderr behavior that would confuse automation

Workflow

Identify the Python entry point or shell wrapper being changed.
Compare it with nearby scripts, docs, and tests so command behavior stays aligned.
Prefer shared payload parsing and JSON error helpers where the contract matches.
Keep shell wrappers thin when Python already owns the logic.
Update docs or smoke tests if the command surface changes.
Run the relevant repo checks.

Expected output

Findings

List mismatches in command behavior, docs, or wrapper layers.

Fixes

Summarize what was simplified or synchronized.

Validation

State the commands or tests you ran.

Definition of done

The tooling surface should be:

consistent across Python, shell, and docs
easy to invoke with current repo commands
free of needless wrapper duplication
covered by the right smoke or regression checks