pm-fix

A triage command that turns pasted error logs or stack traces into recorded bug findings and follow-up tasks. Triage means sorting and describing problems before fixing them.

In plain words
What is it for?
Use it to classify errors, warnings, blank screens, routing failures, and similar issues, compare them with approved project requirements, and suggest the next project-management command.
Why use it?
It captures the likely severity and next action without changing application code before the user approves a fix. Sensitive values are removed from saved evidence.

Command

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add commands/wei63w/pm-manager/pm-fix
Clone the repo
git clone --depth 1 https://github.com/wei63w/pm-manager
Per session 22 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 465 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00022 $0.00465
Opus 5 $0.00011 $0.00233
Sonnet 5 $0.00004 $0.00093
Haiku 4.5 $0.00002 $0.00047

Measured 3d ago against content hash 99e5184f4ebc, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

pm-fix scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

  • fix — 100% identical, 0 lines differ
adapters/claude-code/commands/pm-fix.md · 41 lines

What it actually says

User Input

$ARGUMENTS

Outline

先告诉用户(中文,置顶):本次只分诊,不改代码。要把修复写进仓库,请你明确确认。

  1. Prefer current conversation paste as evidence (first-class; no need to save a file first); else --path / sources / .pm/inbox/stacks/.
  2. Desensitize; write evidence JSON; optionally copy redacted snippet to inbox. Never persist secret originals.
  3. Classify severity (blocking/high/medium/low/suggestion). Vue / Vite 白屏、Vue warn、Pinia、路由失败按同样规则分诊,不改代码。
  4. Append bugs/findings.md + state/todo.md entry with next action.
  5. Charter compare for availability/success criteria with confidence only if charter.status=approved.
  6. Persist a desensitized dialogue note via pm log --kind fix (intent + files the user named; else unresolved — never invent paths). Then pm journal if you need the timeline.
  7. Summarize in Chinese: severity, suggested /pm-next / later /pm-done TODO-xxx. Repeat: 未确认不改业务代码。

Do not modify application code unless user confirms.

Shared Workflow (all /pm-* commands)

  1. Read .pm/config/project.yaml(缺则建议 /pm-init)。
  2. Map-first; incremental; conversation paste highest priority.
  3. Desensitize evidence. Never persist raw secrets.
  4. Draft PRD/charter MUST NOT be used as the baseline.
  5. Merge findings/todos; refresh overview (all blocking+high, no 3-item cap).
  6. Append audit.
  7. Closing: _closing.md 轻量档。

Design baseline: docs/prd.md + 宪章。

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 3d ago First seen · 41 lines · 22 tokens per session scan A 99e5184f4ebc

Subscribe to this mod's changes

pm-fix is a command published in the GitHub repository wei63w/pm-manager (96 stars, last pushed 3d ago), licensed MIT. It adds 22 tokens to every session and 465 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.