Skip to content

Clarify README CLI commands vs in-session skills#2200

Open
Yeachan-Heo wants to merge 2 commits intodevfrom
omc/issue-2198-readme-cli-vs-skills
Open

Clarify README CLI commands vs in-session skills#2200
Yeachan-Heo wants to merge 2 commits intodevfrom
omc/issue-2198-readme-cli-vs-skills

Conversation

@Yeachan-Heo
Copy link
Copy Markdown
Owner

Summary

  • add a focused README section that separates terminal omc ... commands from in-session /... skills
  • show paired CLI + in-session examples where the repo supports both and explicitly call out that autopilot/ralph/ultrawork are not omc subcommands
  • document the existing omc autoresearch CLI surface and its /deep-interview --autoresearch ... handoff

Closes #2198

Verification

  • node bridge/cli.cjs --help
  • node - <<'NODE' ... AUTORESEARCH_HELP ... NODE
  • npm run test:run -- src/cli/__tests__/cli-boot.test.ts src/cli/__tests__/autoresearch.test.ts src/__tests__/auto-slash-aliases.test.ts
  • npx tsc --noEmit

Notes

  • npm run lint still reports one pre-existing warning in src/hooks/setup/__tests__/stdin-symlink.test.ts

The README mixed terminal `omc ...` commands with in-session slash skills, which made features like autopilot and team look interchangeable. This change adds a compact surface guide, relabels the quick-start example as an in-session skill, pairs CLI and slash forms where the repo actually supports both, and documents the existing `omc autoresearch` CLI path.

Constraint: Keep scope tight to README accuracy for issue #2198
Rejected: Broad README rewrite | unnecessary risk and churn for a documentation fix
Confidence: high
Scope-risk: narrow
Reversibility: clean
Directive: When documenting OMC features, verify whether the surface is terminal CLI, in-session skill, or both before adding examples
Tested: node bridge/cli.cjs --help; AUTORESEARCH_HELP from dist/cli/autoresearch.js; npm run test:run -- src/cli/__tests__/cli-boot.test.ts src/cli/__tests__/autoresearch.test.ts src/__tests__/auto-slash-aliases.test.ts; npx tsc --noEmit
Not-tested: Full vitest suite; lint warning cleanup in unrelated existing test file
@chatgpt-codex-connector
Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

@github-actions github-actions bot added the size/S label Apr 5, 2026
Issue #2198 asked for tighter documentation around which entrypoints are real `omc` CLI commands versus in-session skills and prompt triggers. The current README already covered most of the distinction, but the shortcuts table still mixed a terminal example into the in-session section and did not label slash skills versus prompt triggers consistently.

This narrows the README copy to the actual runtime surfaces verified in the repo: in-session shortcuts now stay session-only, Team is called out as explicit on both surfaces, and the table shows slash-skill versus prompt-trigger forms without implying extra CLI subcommands.

Constraint: Keep scope limited to documentation accuracy; no runtime changes
Rejected: Broad README rewrite | unnecessary churn for a small docs issue
Confidence: high
Scope-risk: narrow
Reversibility: clean
Directive: When documenting OMC entrypoints, verify terminal `omc ...` commands in `src/cli/index.ts` and session surfaces in `skills/*/SKILL.md` or slash-command runtime code before adding examples
Tested: node bridge/cli.cjs --help; node bridge/cli.cjs autoresearch --help; npm test -- --run src/cli/__tests__/autoresearch.test.ts src/cli/__tests__/autoresearch-guided.test.ts src/__tests__/auto-slash-aliases.test.ts src/cli/__tests__/team-help.test.ts src/cli/__tests__/ask.test.ts
Not-tested: Localized README variants
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant