PostHog developer CLI and repo tooling reference. Use when the user mentions hogli, asks about repo CLI tools, bin scripts, Makefiles, how to run/build/test/lint, or any dev environment commands.
72
88%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Passed
No findings from the security scan
Unified CLI for PostHog development. Wraps all repo scripts, bin commands, and tooling behind a single entry point. There is no Makefile — hogli is the equivalent.
Run hogli --help to get the full, current command list. Run hogli <command> --help for any subcommand.
Where logs land depends on how the stack was launched:
Detached (hogli up -d) — phrocs writes files under .posthog/.generated/logs/ on every boot:
phrocs.log — the daemon's own stdio; the place to look when phrocs died at startup and the phrocs MCP tools are unreachable.<process>.log — per-process output (truncated on each start), where <process> matches the phrocs process key (see bin/mprocs.yaml).hogli doctor:report prints the phrocs.log path and tails its last lines.TUI with hogli dev:setup --log, then hogli start — adds a tee wrap per process:
/tmp/posthog-<process>.log — full stdout+stderr; persists in the generated config until dev:setup is re-run without --log.When the phrocs MCP is reachable, prefer mcp__phrocs__get_process_logs over grepping files.
hogli.yaml — command definitions (source of truth)tools/hogli-commands/hogli_commands/ — PostHog-specific lazy Click command modulestools/hogli/README.md — framework documentationtools/hogli-commands/README.md — PostHog commands documentationd1dd198
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.