agentleFS
Sign inStart free
PostHogKnown publisherPostHog/posthog-foss/.agents/skills/hogli/SKILL.md

hogli

Skill727 starsChanged yesterdayMITView on GitHub

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.

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run hogli --help to get the full, current command list.

    line 13
  2. Very specific:

    When the phrocs MCP is reachable, prefer mcp__phrocs__get_process_logs over grepping files.

    line 29

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free