pythinker-code

Reduction-ladder and minimum-diff checks the Pythinker judge subagent applies to every non-trivial diff.

Over-engineering review checklist the parent runs before declaring non-trivial code changes done.

Whole-repo audit for over-engineering and accidental complexity. Scans the entire codebase (not just a diff) and returns a ranked, read-only list of what to delete, simplify, or replace with standard-library or platform equivalents. Use when the user asks to "audit the codebase", "find bloat", "what can I delete", or wants a repo-wide simplification pass. For a diff-scoped pass use `pythinker review diff --mode deslopify` instead. One-shot report; applies no fixes.

Prescriptive frontend design guidance via the designer-skill MCP server. Use when the user asks to use designer-skill, improve UI/UX, run the anti-slop ship gate, apply a design system, or enhance pages/components with MCP-backed design references — especially for Pythinker docs and marketing surfaces with DESIGN.md/PRODUCT.md.

Author a new project-specific Pythinker subagent (a specialist like "migration-reviewer" or "api-contract-checker") with a correct spec, a persona-rich system prompt, and a structured output contract. Use when the user wants to create, scaffold, or design a custom agent / subagent, or asks how Pythinker agent YAML / markdown agent files, tool scoping, or the extend-inheritance schema work.

Edit Pythinker's own configuration — agent YAML specs and extend-inheritance, the permission profiles that gate tools, plugin.json, and hook lifecycle events. Use ONLY when the user wants to configure, customize, or extend Pythinker itself (its agents, permissions, plugins, or hooks). For authoring a new agent use agent-creator; for authoring a skill use skill-creator; for general usage Q&A use pythinker-code-help.

Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Pythinker's capabilities with specialized knowledge, workflows, or tool integrations.

Answer Pythinker CLI usage, configuration, and troubleshooting questions. Use when user asks about Pythinker CLI installation, setup, configuration, slash commands, keyboard shortcuts, MCP integration, providers, environment variables, how something works internally, or any questions about Pythinker CLI itself.

Execute the release workflow for Pythinker CLI packages.

Produce a concise reviewer-friendly walkthrough of a PR or diff, including changed areas, behavior, tests, and risks.

Reproduce a bug report with evidence-first investigation, bounded variants, and a clear repro/non-repro verdict.

Draft a product spec from a user request, issue, or bug report with goals, non-goals, requirements, and acceptance criteria.

Draft a technical implementation spec from product requirements and codebase evidence.

Compare an implementation against a product or technical spec and report gaps with evidence.

Prepare a pull request by summarizing changes, verification, risks, and reviewer guidance without adding AI footers.

Fix concrete errors from logs, failing commands, exceptions, or diagnostics with root-cause-first discipline.

Implement one or more checked-in specs using scout-plan-implement-verify workflow.

Resolve git merge/rebase conflicts safely by preserving both sides' intent and validating the result.

Diagnose failing CI, lint, typecheck, build, or test logs and propose or implement the smallest verified fix.

Review a pull request or working-tree diff with severity-scored, evidence-backed findings.

Implement a feature or fix from product/technical specs while checking the final code against the stated requirements.

Sync Rust implementation with Python changes (exclude UI/login) by reviewing recent changes, mapping modules, porting logic, and updating tests.

Sample plugin demonstrating the Skills + Tools model. Includes a Python tool (greeting) and a TypeScript tool (calculator).