| 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
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.mddocs/engineering/DEV.mdscripts/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
