بنقرة واحدة
hm-status
Run the harness-mem status daily action when the user invokes hm-status.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
القائمة
Run the harness-mem status daily action when the user invokes hm-status.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Run the harness-mem distill daily action when the user invokes hm-distill.
Run the harness-mem distill daily action when the user invokes hm-distill.
Evidence answerer for harness-mem memory admission and review. Use when grill-before-distill or review needs concrete support from packet evidence, observations, memory search, files, docs, tests, config, or command output. Does not write candidates or confirmed truth.
Architecture, product-boundary, roadmap, and long-lived-rule consultation for harness-mem memory admission and review. Use when a candidate's truth depends on design judgment rather than only evidence lookup. Does not write memory.
Standard memory admission mode for harness-mem (grill-me role). Runs automatically on distill — depth scales by risk, not a forced heavy loop every time. Three modes: deep interrogation, light checklist, lookback for stale truth. No writes. More than a review-stage helper: admission plus lookback.
Conversation autopilot for harness-mem. Use proactively when starting or resuming a task, when the user asks about previous decisions, when the user asks to remember a rule, when recent work becomes stable enough to preserve, or when a memory conflict appears.
| name | hm-status |
| description | Run the harness-mem status daily action when the user invokes hm-status. |
This is a user-invocable harness-mem Daily command. Follow the action below through the configured harness-mem MCP server; do not replace it with terminal maintenance commands.
通过 MCP 显示当前项目的记忆状态,并给出 slash-first 下一步建议。
Input: 可指定项目($hm-status bazi-apps),省略则用 active project。
Steps
调 MCP get_project_status(project_root=<当前工作区>, host_client="codex")(带项目参数如果有;省略项目名时按目录解析)
解析结果,重点关注:
phase / suggested_slash / reasonrepair_hint / repair_reasonruntime_versions / job_health / retrieval_healthcost_budget 最近高成本调用与建议install_drift stale registration / 旧 slash command 风险用自然语言总结给用户,并给出具体可点的 slash 建议:
phase=needs-distill → 建议用户跑 $hm-distillphase=ready → 建议 $hm-wakerepair_hint=$hm-review,把它表述成显式复查/纠错入口,不要把 review 说成日常必经步骤只有用户明确追问 provenance、老 pending 细节或最近历史时,才继续调更低层读取面:
timelinelist_candidates$hm-status 不需要为了给下一步建议而手工拼这些低层工具。Notes