solvcon

Apply solvcon's judgment-call C++ style rules (m_ prefix, class/struct/namespace ending marks, function-body placement, SimpleCollector preference, pybind11 binding split, const_cast) to changed lines in cpp/ or gtests/. Use after editing C++ sources.

Apply solvcon's judgment-call Python style rules (naming, project conventions, test intent) to changed lines in solvcon/ or tests/. Use after editing Python sources.

Enter an isolated git worktree and do the task there. Use when the user wants to avoid polluting the main working tree.

Open a solvcon pull request that follows the project PR protocol (concise subject, clear description, "related to

Draft prototype on a personal fork paired with a served development-plan doc, keeping the upstream repository clean.

Build the solvcon Sphinx docs and serve them on specified network with guaranteed teardown when the Claude session ends. Use when the user asks to build and serve the documentation, preview the docs, or share the rendered docs online.

Commits changes the solvcon way -- splits work into one-concern commits, lints first, stages exact paths, and writes STYLE.md-conformant messages (imperative subject, no semantic prefixes, no closing keywords, human-authored). Use when the user asks to commit, split work into commits, organize or rewrite commit history, or write a commit message.