Menú
Enter an isolated git worktree and do the task there. Use when the user wants to avoid polluting the main working tree.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
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.
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.
| name | worktree |
| description | Enter an isolated git worktree and do the task there. Use when the user wants to avoid polluting the main working tree. |
Use an automatically provided worktree. Otherwise create one, then do the task. No extra ceremony.
If the agent or session already provides a worktree, enter it. Otherwise derive a short kebab-case name from <description>, or omit it and let the tool pick one.
Based on the agent type, do one of the following:
EnterWorktree with that name. If the worktree does not exist, it will be created automatically./worktree command instead. If the built-in command is unavailable, fall back like Codex below.git worktree add -b worktree-<name> .claude/worktrees/<name> origin/master, then run all commands from it.Implement <description> in the worktree. Follow normal project rules. Stop when done; do not auto-commit, open a PR, or remove the worktree unless asked.