Agents Reference¶

WuMing routes each changed file to one or more agents based on glob patterns. Agents run concurrently. A file can be reviewed by multiple agents (e.g. a Python file is reviewed by both code and security).

Configure which agents run via WUMING_AGENTS — see Configuration.

code¶

Reviews source code for correctness, logic bugs, missing error handling, and test coverage gaps.

File patterns: *.py, *.go, *.ts, *.tsx, *.js, *.jsx, *.rs, *.java, *.c, *.cpp, *.h, *.cs

config¶

Reviews configuration and settings files for schema correctness, missing required fields, insecure defaults, exposed secrets, and consistency with documented options.

File patterns: *.toml, *.yaml, *.yml, *.json, *.ini, *.env, *.cfg

docs¶

Reviews documentation files for clarity, accuracy, completeness, broken links, and formatting issues.

File patterns: *.md, *.rst, *.txt

security¶

Reviews code, config, and shell files from an OWASP Top 10 (2021) perspective. Looks for injection flaws, broken authentication, sensitive data exposure, security misconfigurations, use of components with known vulnerabilities, and related issues. Runs alongside the other agents as an additive reviewer, not a replacement.

File patterns: same as code + config + shell combined — *.py, *.go, *.ts, *.tsx, *.js, *.jsx, *.rs, *.java, *.c, *.cpp, *.h, *.cs, *.toml, *.yaml, *.yml, *.json, *.ini, *.env, *.cfg, *.sh, *.fish, Dockerfile, Containerfile, Makefile

shell¶

Reviews shell scripts and infrastructure files for correctness, security risks (injection, exposed secrets), error handling, portability, and CI/CD pipeline correctness.

File patterns: *.sh, *.fish, Dockerfile, Containerfile, Makefile

Per-agent model selection¶

Any agent can use a different model from the rest of the pipeline. Append :model to the agent name in WUMING_AGENTS:

WUMING_AGENTS=code:deepseek-chat,security:deepseek-reasoner,config

When a deepseek-reasoner model is selected for an agent, WUMING_MAX_TOKENS is automatically raised to 16384 for that agent's call, regardless of the global setting.

Model names are backend-specific — use the exact model identifier accepted by the backend you have configured in WUMING_BACKEND. The example above uses DeepSeek model names; substitute the appropriate identifier for Anthropic or Ollama backends.