Run any Skill in Manus with one click

code-quality-review

Stars1

Forks0

UpdatedApril 2, 2026 at 18:35

Review and improve Python code quality in SoulMap AI so typing, helper usage, exception handling, and repo tooling conventions stay consistent.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

tuanductran

tuanductran/soulmap-ai

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software Quality Assurance Analysts and TestersComputer and Mathematical Occupations·SOC 15-1253

SKILL.md

readonly

name	code-quality-review
description	Review and improve Python code quality in SoulMap AI so typing, helper usage, exception handling, and repo tooling conventions stay consistent.

Code quality review

Use this skill when reviewing or improving Python implementation quality in src/, compatibility wrappers, tests/, or scripts/.

Do not use this skill for

product doctrine or response-safety review, use ai-prompt-engineering-safety-review
eval suite design, use eval-suite-maintainer
packaging and release checks, use packaging-maintainer

Mission

Keep Python changes clear, typed, maintainable, and consistent with the repo's existing tooling contract.

Sources to check first

pyproject.toml
../rules/python-tooling.md
../rules/source-character-safety.md
docs/engineering/DEV.md
the target Python files and nearby tests

What to look for

stale or duplicated helper logic
weak typing or type drift against repo conventions
broad exception handling or hidden failure paths
dead branches, unused fields, or wrappers that add no value
local code that should use shared helpers in src/soulmap/runtime/io/cli_payload.py or src/soulmap/runtime/io/text_normalization.py

Workflow

Read the target Python files and the closest tests first.
Compare the implementation with pyproject.toml and ../rules/python-tooling.md.
Identify concrete quality issues that affect clarity, correctness, or maintenance.
Make the smallest correct change that improves the code without widening scope.
Update tests when the observable contract changes.
Run the repo checks needed for the touched files.

Expected output

Findings

List the concrete code-quality issues first.

Fixes

Summarize the changes that improved type safety, helper usage, or readability.

Validation

State which checks were run and whether they passed.

Definition of done

The updated code should be:

simpler or clearer than before
aligned with repo tooling rules
free of obvious duplicated logic
covered by the right tests for the changed behavior

More from this repository

same repository

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	code-quality-review
description	Review and improve Python code quality in SoulMap AI so typing, helper usage, exception handling, and repo tooling conventions stay consistent.

Code quality review

Use this skill when reviewing or improving Python implementation quality in src/, compatibility wrappers, tests/, or scripts/.

Do not use this skill for

product doctrine or response-safety review, use ai-prompt-engineering-safety-review
eval suite design, use eval-suite-maintainer
packaging and release checks, use packaging-maintainer

Mission

Keep Python changes clear, typed, maintainable, and consistent with the repo's existing tooling contract.

Sources to check first

pyproject.toml
../rules/python-tooling.md
../rules/source-character-safety.md
docs/engineering/DEV.md
the target Python files and nearby tests

What to look for

stale or duplicated helper logic
weak typing or type drift against repo conventions
broad exception handling or hidden failure paths
dead branches, unused fields, or wrappers that add no value
local code that should use shared helpers in src/soulmap/runtime/io/cli_payload.py or src/soulmap/runtime/io/text_normalization.py

Workflow

Read the target Python files and the closest tests first.
Compare the implementation with pyproject.toml and ../rules/python-tooling.md.
Identify concrete quality issues that affect clarity, correctness, or maintenance.
Make the smallest correct change that improves the code without widening scope.
Update tests when the observable contract changes.
Run the repo checks needed for the touched files.

Expected output

Findings

List the concrete code-quality issues first.

Fixes

Summarize the changes that improved type safety, helper usage, or readability.

Validation

State which checks were run and whether they passed.

Definition of done

The updated code should be:

simpler or clearer than before
aligned with repo tooling rules
free of obvious duplicated logic
covered by the right tests for the changed behavior