Boost: Factory Logrus Backend

What it does

This skill documents how to replace the default zerolog backend in the xgodev/boost framework with Sirupsen logrus safely. It explains the required initialization order (call log.Set after boost.Start), how to construct the factory-provided logrus logger (including passing native hooks), and how the formatter is chosen via the boost.factory.logrus.formatterType (TEXT/JSON/CLOUDWATCH). It also lists config keys and recommended environment overrides.

When to use it

Use this skill when migrating or configuring a Go service that imports the boost framework and needs logrus as the backend (for compatibility with existing hooks, Sentry/datadog integrations, or specific formatter behavior). It's applicable when you see imports under factory/contrib/sirupsen/logrus, or when env vars like BOOST_FACTORY_LOGRUS_* are present.

What's included

• Scripts: none included; the skill provides code examples and configuration keys to change.
• References: points to factory implementation and config.go for the boost.factory.logrus tree.
• Instructions: a concise example showing import, boost.Start(), and log.Set(logrus.NewLogger(...)), plus a table of config keys and common red flags with fixes (e.g., wrong init order, global hooks, per-request logger creation).

Compatible agents

Best for Go-aware agents that can read and suggest code changes, run linters/build commands, and edit Go source files (agents with Bash(go:*) or Golang tooling).