Help

Asking for help

You do not have to come to this wiki yourself. The skill has a help branch: ask your agent a question about PlanX and it reads the page that covers it and answers in chat.

Agent	Type
Claude Code	/planx help <question>
Codex	$planx help <question>
Another agent	The PlanX skill invocation syntax that agent supports

/planx help how do I comment on a single line?
/planx help what can you do?
/planx help what does s do in the review?
/planx help where are my plans stored?
/planx help can I plan in Claude Code and build in Codex?

The answer comes back in a few lines, with a link to the page it came from. No plan is created, no version is captured, and nothing in ~/.planx is touched — it is a read, and it ends when the question is answered.

For a broad question such as what can you do?, the answer gives you the core workflow, the important review features, agent support and the quickest way to start. It does not dump every command and key into the chat.

What it actually does

Every page of this wiki is a file of markdown, and the raw form of it is fetchable:

https://raw.githubusercontent.com/wiki/thisisnsh/planx/Reviewing.md

The skill maps the question to a page, fetches that one page, and answers from it. When nothing in its map fits, it fetches Home — which indexes every page — and routes from there. That second step matters: the map ships inside the skill and is only as new as your installed version, while the wiki changes whenever the docs do.

So the answer you get is what this wiki says today, not what the model remembers about PlanX. Where the two disagree, the page wins.

help is about PlanX, not about your work

The branch is chosen on the word help, which is also a word people start tasks with. The rest of the line decides:

You typed	What happens
/planx help how do I fold a section?	Answered from the wiki
/planx help me split the auth module	Planned, like any other task

The first asks about PlanX. The second asks for work on your repository, and gets the plan branch — clarify, research, write, capture, stop. When a line genuinely reads both ways, the agent asks which you meant before it does either.

When the wiki does not answer it

It says so, rather than inventing a key or a flag that sounds right. An answer that is nearly correct costs you a session finding out it was never real.

Questions the wiki does not cover belong in Q&A, where they get answered once for everybody — and things PlanX does not do yet belong in Ideas.

If it cannot reach the wiki

An agent with no network, or a sandbox that blocks it, cannot take this branch. It will tell you so; read the page yourself from the sidebar, or ask in Q&A.

Questions about the exact version installed on your machine — a flag, a default — are better answered by planx --help and planx <command> --help anyway. The agent runs those too when the question is version-specific.

Related

• The skill — every branch, and how the agent dispatches on them
• FAQ — short answers, one question at a time
• Troubleshooting — when something is not where you expect it