Agent skill · Databases

pm-fix

Analyze pasted logs/stacks/slow SQL from chat (or --path) into bugs findings and todos.

carrot36★ · 1 repos on radarProfile →
cursorclaude-codeMIT
Install
npx skills add wei63w/pm-manager --skill pm-fix --agent cursor

Same command for any agent — swap --agent for claude-code, codex, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 2 KB
Bundled scripts: none
Path: adapters/cursor/skills/pm-fix/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 69
Language: Python

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

## User Input ```text $ARGUMENTS ``` ## Outline 1. Prefer **current conversation paste** as evidence; else `--path` / sources / `.pm/inbox/stacks/`. 2. Desensitize; write evidence JSON; optionally copy redacted snippet to inbox. 3. Classify severity (blocking/high/medium/low/suggestion) per design rules. 4. Append `bugs/findings.md` + `state/todo.md` entry with next action. 5. Charter compare for

More from pm-manager
All skills →
About this skill
What does the pm-fix skill do?

Analyze pasted logs/stacks/slow SQL from chat (or --path) into bugs findings and todos.

How do I install it?

Run `npx skills add wei63w/pm-manager --skill pm-fix --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From wei63w/pm-manager, a repository with 69 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going