backend/.claude/skills/errorcode/SKILL.md
Manages error code allocation and governance across the codebase. Use this skill when the user wants to list, query, allocate, check, add, update, or sync error codes. Invoked via /errorcode. Enforces SSOT registry, sequential allocation, and conflict prevention.
npx skillsauth add lunay77/ello-bot errorcodeInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
You are the Error Code Manager Agent. You own end-to-end governance of error code allocation and synchronization across:
.claude/skills/errorcode/assets/error-code-ranges.yamlnext_available is the only valid next code.All operations go through python3 .claude/skills/errorcode/scripts/errorcode.py:
python3 .claude/skills/errorcode/scripts/errorcode.py list
python3 .claude/skills/errorcode/scripts/errorcode.py query <domain>
python3 .claude/skills/errorcode/scripts/errorcode.py allocate <domain> --description "<text>" --location "<path>" [--source business|framework|third_party]
python3 .claude/skills/errorcode/scripts/errorcode.py check --description "<text>"
python3 .claude/skills/errorcode/scripts/errorcode.py add <domain> <name> --message "<text>"
python3 .claude/skills/errorcode/scripts/errorcode.py update <domain> <added_code>
python3 .claude/skills/errorcode/scripts/errorcode.py sync
Add --json to any command for machine-readable output.
check --description "<描述>" — find reusable codes firstadd <domain> <NAME> --message "<message>"allocate <domain> --description "<text>" --location "<file path>"{Source}{DD}{NN}
A = framework, B = business, C = third_partyDD = 2-digit domain id (01–99)NN = 2-digit sequential id (00–99)xx00–xx99.claude/skills/errorcode/assets/error-code-ranges.yaml (project-relative)
If missing, the script creates it automatically from the standard template.
development
Maintainer-only workflow for handling GitHub Secret Scanning alerts on OpenClaw. Use when Codex needs to triage, redact, clean up, and resolve secret leakage found in issue comments, issue bodies, PR comments, or other GitHub content.
development
Maintainer workflow for OpenClaw releases, prereleases, changelog release notes, and publish validation. Use when Codex needs to prepare or verify stable or beta release steps, align version naming, assemble release notes, check release auth requirements, or validate publish-time commands and artifacts.
development
Run, watch, debug, and extend OpenClaw QA testing with qa-lab and qa-channel. Use when Codex needs to execute the repo-backed QA suite, inspect live QA artifacts, debug failing scenarios, add new QA scenarios, or explain the OpenClaw QA workflow. Prefer the live OpenAI lane with regular openai/gpt-5.4 in fast mode; do not use gpt-5.4-pro or gpt-5.4-mini unless the user explicitly overrides that policy.
development
End-to-end Parallels smoke, upgrade, and rerun workflow for OpenClaw across macOS, Windows, and Linux guests. Use when Codex needs to run, rerun, debug, or interpret VM-based install, onboarding, gateway smoke tests, latest-release-to-main upgrade checks, fresh snapshot retests, or optional Discord roundtrip verification under Parallels.