agentleFS
Sign inStart free
LedgerHQLedgerHQ/ledger-live/.agents/skills/console-log/SKILL.md

console-log

Skill627 starsChanged 8 days agoMITView on GitHub

Choose between `console.warn`, `console.error` and no log at all, knowing Datadog RUM reports every `console.error` as an error event. Read when adding or changing a `console.error`, `console.warn` or `console.log` call in app or package code, or when Datadog shows error events for expected or recoverable failures.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use console.warn for expected or recoverable errors (network failures, optional feature unavailable, etc.)

    line 10
  2. Very specific:

    Use console.error only for illegal/unexpected program states that should never occur in production

    line 11
  3. Distinctive:

    Prefer dropping the log entirely when the error is neither actionable nor surprising

    line 12

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Console Logging Convention

console.error is intercepted by Datadog RUM and forwarded as an error event.

  • Use console.warn for expected or recoverable errors (network failures, optional feature unavailable, etc.)
  • Use console.error only for illegal/unexpected program states that should never occur in production
  • Prefer dropping the log entirely when the error is neither actionable nor surprising

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free