Menu

Individual skill

log-message-improver

Improves logging statements for observability - structured logging, appropriate log levels, and useful context. Use when logs are too sparse, too noisy, or missing the context needed to debug an incident from them alone.

skills/utilities/log-message-improver/SKILL.md

Read pinned source

Source commit d0a9928d24afb7df0fad2f2f35f65d3938a6926a

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Instructions only
Last checked
Nov 5, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
27
Repository last updated
Aug 20, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

## Purpose

Improve logging statements so they're actually useful during an incident or investigation — the right level, structured (not just string concatenation), and carrying the context a future reader will need without access to the original author's memory of what was happening.

## When to Use

- Logs are too sparse to debug an issue from, or too noisy to find the signal.
- Adding logging to new code and want it done well from the start.
- Reviewing logging statements in a PR.

## What to Analyze

1. **Log level appropriateness** — is this actually an error (something broke) or just unusual-but-expected (should be warn/info)? Overuse of `error` for expected conditions trains people to ignore error-level alerts.
2. **Structured vs. string-concatenated** — `log.info(\`User ${id} did ${action}\`)` is harder to query/filter than `log.info('user_action', { userId: id, action })` — prefer structured fields where the logging framework supports it.