Logging examples
Worked, detailed logging examples — each level demonstrated in an order-processing scenario, a state-machine transition example, and a unified production-style example. Use when writing or reviewing logging code and you want concrete examples beyond the logging best-practices rules (which are already resident in context). Tech-stack agnostic.From its SKILL.md
npx -y skills add ikonglong/entapp-dev --skill logging-examplesAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.6 KB, as published. Nobody here has run it
Logging Examples
The logging rules — the six levels and how to choose one — are already
resident in your context (from logging-best-practices.md). This skill points
you to the detailed examples, which are kept out of context until you need
them.
All three example files live in this plugin's knowledge/logging/ directory —
the same directory as logging-best-practices.md. From this skill's base
directory, that path is ../../knowledge/logging/. Read whichever you need, in
full, using an absolute path (join this skill's base directory with the relative
path):
logging-examples-by-level.md— each level (FATAL … TRACE) demonstrated independently in an order-processing scenario.logging-unified-example.md— all levels coexisting in one function; key principle: lower levels add detail, they do not repeat.logging-state-machine-example.md— logging state transitions; key principle: each transition is a business milestone (INFO), and volume is not a reason to downgrade.
These files are reference material — read them, do not modify them. They illustrate principles, not templates: understand the reasoning behind each logging decision and adapt it to your own context rather than copying verbatim.