Skill Store 33

Hogli

PostHog developer CLI and repo tooling reference.

by posthog · MIT

The skill

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.

hogli - PostHog Developer CLI

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.

Process logging (for agents/debugging)

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.

Key references

  • hogli.yaml — command definitions (source of truth)
  • tools/hogli-commands/hogli_commands/ — PostHog-specific lazy Click command modules
  • tools/hogli/README.md — framework documentation
  • tools/hogli-commands/README.md — PostHog commands documentation

Use this skill

Connect your agent to the Skill Store MCP server and ask for it by ref: posthog/hogli-50407169415.

Download SKILL.md · Markdown version

Details

Publisher
posthog
Category
Software Development › Developer docs & tooling
License
MIT
Updated
2026-10-19

References

More from posthog