Skip to content

docs: Document the signals and facts CLI commands - #65

Draft
huacnlee wants to merge 1 commit into
mainfrom
docs/signals-commands
Draft

huacnlee wants to merge 1 commit into
mainfrom
docs/signals-commands

Conversation

@huacnlee

Copy link
Copy Markdown
Member

Adds the three new CLI commands to the Longbridge skill.

  • SKILL.mdsignals / signal <id> / facts SYMBOL.US in the quick reference, under the news-and-catalyst block where an agent already looks for catalysts.
  • references/cli/overview.md — a short section on the signal ↔ catalyst-fact relationship: the list omits the multi-KB strategy analysis, signal <id> --format json carries it under analysis, and a signal names its trigger in key_fact_id which facts resolves on the same symbol.

Kept high-level per the repo's convention — flag details stay in longbridge --help.

Draft on purpose — blocked on longbridge/longbridge-terminal#309, which adds the commands. Mark ready once a CLI release ships them, so the skill never describes commands the installed binary does not have.

🤖 Generated with Claude Code

Adds `signals` / `signal` / `facts` to the quick reference and a short section
in the CLI overview explaining the signal ↔ catalyst-fact relationship: the
list omits the multi-KB strategy analysis, `signal <id> --format json` carries
it, and a signal names its trigger in `key_fact_id`.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant