菜单
Run quality control checks on the codebase — type checking, linting, tests, and server smoke test. Use when the user says "/qc", wants to verify code quality, or after making significant changes.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Save or update the current session. Use this skill when asked to handoff, save session, update session, start a new chat, etc. Always call this before using the `update_session` MCP tool directly.
Generate or update CHANGELOG.md from git commits using semantic versioning. Use when the user says "/changelog", wants to update the changelog, or asks to generate release notes.
Find typos, grammar errors, punctuation/capitalization mistakes, and banned-phrase voice slips in prose and code comments. Use when the user says "/typo-check", wants to scan for typos, or before shipping user-facing text. Reports findings and confirms before fixing.
Commit, docs, changelog, and push in one go. Use when the user says "/ship", wants to ship their changes, or asks to commit and push everything.
Import conversation history from AI providers (Claude, Copilot, Codex, Cursor) and generate stories from the imported data. Use on first session to bootstrap memory from existing conversations, or anytime the person wants to import history from another provider/machine.
Research a topic and save findings to Charlieverse knowledge. Use whenever the user wants to research something, look up documentation, investigate a library or tool, explore a concept, or asks "what do you know about X". Also trigger when the user says "/research", wants to build up knowledge about a subject, or asks you to "look into" something — even if they don't use the word "research" explicitly.
| name | qc |
| description | Run quality control checks on the codebase — type checking, linting, tests, and server smoke test. Use when the user says "/qc", wants to verify code quality, or after making significant changes. |
| argument-hint | [scope: all|types|tests|smoke (default: all)] |
Runs a multi-stage quality control pipeline: type checking, linting, unit tests, and a live server smoke test. Reports pass/fail for each stage with details on failures.
uv run ty check
Report the number of diagnostics. Zero is the target — any failures should be listed with file and line.
uv run pytest tests/ -v --tb=short 2>&1
Report pass/fail counts. If tests don't exist yet, note that and skip (don't fail QC for missing tests during early development).
Start the server if it's not already running:
charlie server status
If not running, start it:
charlie server start
Wait for health:
curl -s http://localhost:8765/api/health
Then verify REST endpoints respond with valid JSON:
curl -s http://localhost:8765/api/entities | head -c 200
curl -s http://localhost:8765/api/knowledge | head -c 200
curl -s http://localhost:8765/api/stories | head -c 200
Check all return JSON (arrays or objects, not HTML or errors).
Then verify MCP tools work by calling recall through the CLI:
charlie hooks session-start 2>&1 | head -c 500
Check that activation context is generated (contains XML tags or markdown). This exercises the full MCP → store → context pipeline.
curl -s http://localhost:8765/ | grep -c '<div id="root">'
Verify the SPA index.html is served.
Summarize results:
| Check | Status |
|---|---|
| Type checking | X diagnostics |
| Tests | X passed, X failed |
| Server health | OK/FAIL |
| MCP tools | OK/FAIL |
| REST API | OK/FAIL |
| Web dashboard | OK/FAIL |
If any stage fails, list the specific failures with enough detail to fix them.
If $ARGUMENTS specifies a scope:
types — only run type checkingtests — only run testssmoke — only run server smoke testall (default) — run everything