Use `Warn` for expected-but-notable errors like `user not found` when they can happen in normal flow and are worth observing. Use `Error` for unexpected failures you need to investigate. Panics are not normal control flow, so log them at `Error` or higher with full context, then recover or crash at the boundary that owns the process. As a rule of thumb: - `Info`: normal events - `Warn`: expected anomalies or client/domain issues - `Error`: unexpected failures, broken dependencies, recoverable...
Scanned 9/5/2026
Install to Claude Code
Skills Directorynpx -y skills add HoangNguyen0403/agent-skills-standard --skill golang-logging --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Golang Logging?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/hoangnguyen0403-golang-logging-b832a8d8)More formats (shields.io, HTML) on the badges page.
Use `Warn` for expected-but-notable errors like `user not found` when they can happen in normal flow and are worth observing. Use `Error` for unexpected failures you need to investigate. Panics are not normal control flow, so log them at `Error` or higher with full context, then recover or crash at the boundary that owns the process.
As a rule of thumb:
- `Info`: normal events
- `Warn`: expected anomalies or client/domain issues
- `Error`: unexpected failures, broken dependencies, recoverable server faults
If `user not found` is a totally normal lookup result, you may not need to log it at all, or log it at `Debug` to avoid noise.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Use this skill when developing or maintaining browser extension code in the `browser/` directory, including Chrome/Firefox/Edge compatibility, content scripts, background scripts, or i18n updates.
