hogli

Run, build, test, and lint the PostHog codebase via a unified CLI.

693|111|Updated Aug 11, 2020
One-click install
npx skills add https://github.com/PostHog/posthog-foss --skill hogli
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hogli
Source: https://github.com/PostHog/posthog-foss/tree/main/.agents/skills/hogli
Command: npx skills add https://github.com/PostHog/posthog-foss --skill hogli

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a unified command-line interface for all PostHog development tasks, eliminating the need to remember or manage individual scripts and Makefiles.

Core Features & Use Cases

  • Unified Command Entry: Access all repository scripts, bin commands, and tooling through a single hogli command.
  • Developer Environment Management: Simplifies running, building, testing, and linting the PostHog codebase.
  • Debugging Assistance: Offers options for enhanced logging to aid in troubleshooting development processes.
  • Use Case: A developer needs to run the test suite for the PostHog project. Instead of navigating complex directory structures or remembering specific script names, they can simply use hogli test.

Quick Start

Run hogli --help to see all available commands.

Frequently Asked Questions about hogli

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run tests and build the PostHog codebase without managing individual scripts?

You can run tests and build the PostHog codebase through a unified CLI that wraps all repository scripts and bin commands. Simply execute commands like hogli test or hogli build to manage development tasks without navigating directory structures.

What is the best way to lint a PostHog repository using a single command line interface?

The best way to lint the PostHog repository is using a unified developer CLI that consolidates all tooling commands. Running hogli lint executes the necessary linting scripts defined in the codebase without requiring you to remember specific script names.

Can I get enhanced process logging when setting up the PostHog development environment?

Yes, you can get enhanced process logging by running hogli dev:setup --log. This option provides detailed logging output to assist with troubleshooting and debugging the development environment setup process.

Where are the custom commands defined for the PostHog developer command line tool?

Custom commands for the PostHog developer CLI are defined in common/hogli/commands.py, while standard command definitions are referenced in common/hogli/manifest.yaml. These files dictate the available operations for the codebase.

Does the hogli CLI require external dependencies to manage the PostHog development workflow?

No, the hogli CLI does not require external dependencies to manage the PostHog development workflow. It directly references internal repository scripts and commands to facilitate running, building, testing, and linting the codebase.