agentleFS
yeaboi-aiyeaboi-ai/yeaboi.ai/.agents/skills/logging/SKILL.md

logging

Skill4 starsChanged 57 days agoMITView on GitHub

Central logging rules — logging_setup.py handlers, mode_log context manager, per-session logs, log directories from paths.py, LOG_LEVEL, the never-log-per-frame rule. Use when adding logging, creating new log files, or touching logging_setup.py or paths.py.

  • Reads credentials

26 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use convention-learner, modern-csharp and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • codewithmukeshSkill

    convention-learner

    Detects and enforces project-specific coding conventions by analyzing existing codebase patterns. Learns naming conventions, folder structure, test organization, and coding style from the existing code. Load when: "conventions", "coding standards", "project patterns", "enforce style", "detect patterns", "learn conventions", "code consistency".

    Also in 3 projects that use this

  • MovGP0Skill

    modern-csharp

    Modern C# style guidance for Bendex and MicroSea code changes, including primary constructors, expression-bodied members, var usage, target-typed new, lambdas, and pattern matching.

    Also in 3 projects that use this

  • codewithmukeshSkill

    opentelemetry

    OpenTelemetry observability for .NET 10 applications. Covers traces, metrics, and logs using the OpenTelemetry SDK with OTLP export. Includes custom ActivitySource, IMeterFactory metrics, resource configuration, and Aspire Dashboard integration. Load this skill when setting up distributed tracing, custom metrics, OTLP export, or when the user mentions "OpenTelemetry", "OTLP", "traces", "spans", "Activity", "ActivitySource", "metrics", "IMeterFactory", "Meter", "Counter", "Histogram", "Gauge", "telemetry", "observability", "distributed tracing", "OTEL", or "Aspire Dashboard".

    Also in 3 projects that use this

  • vmoranvSkill

    configuration

    配置参考:环境变量、profile、阈值等全部配置项说明

    Also in 4 projects that use this

  • wpankSkill

    caching

    Caching strategies, invalidation, eviction policies, HTTP caching, distributed caching, and anti-patterns. Use when designing cache layers, choosing eviction policies, debugging stale data, or optimizing read-heavy workloads.

    Also in 4 projects that use this

  • HamzaSheikh768Skill

    dependency-injection

    Leverages FastAPI's powerful Depends system for reusable authentication, database sessions, rate limiting, and business logic injection.

    Also in 4 projects that use this

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 21 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

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

    All paths defined in src/yeaboi/paths.py — never hardcode Path.home() / ".yeaboi"

    line 25

“Common” is measured: kept by at least 6 in 10 of the 21 edited versions of this file we could read. “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

Logging

All handler setup lives in src/yeaboi/logging_setup.py — one shared format, one fallback level (WARNING), rotation everywhere (2 MB, 3 backups). Never build a FileHandler inline; use the central module:

  • configure_logging() — attaches the always-on main log (~/.yeaboi/logs/tui/yeaboi.log); called once early in cli.main()
  • with mode_log("<mode>"): — routes all records to ~/.yeaboi/logs/<mode>/<mode>.log while a mode page runs (standup, retro, performance, reporting, analysis). Idempotent + detaches on exception. The analysis branch uses explicit attach_mode_handler/detach (too large for a with block)
  • attach_session_log(session_id) / detach_session_log() — per-planning-session log (~/.yeaboi/logs/planning/{session-id}.log); called via persistence.attach_session_logger
  • apply_level(level) — retunes the yeaboi logger + every attached handler live (used by the Settings page)

Log files:

  • Main/TUI: ~/.yeaboi/logs/tui/yeaboi.log (always on)
  • Per mode: ~/.yeaboi/logs/{standup,retro,performance,reporting,analysis,news}/<mode>.log — active while that page runs; the scheduled headless standup (--standup-run) also writes standup/standup.log; the front page's feed refresh (news/desk.py) writes news/news.log
  • Planning sessions: ~/.yeaboi/logs/planning/{session-id}.log (deleted with the project, including .log.N rotation backups)
  • Desktop backend: ~/.yeaboi/logs/app/app.log — everything yeaboi app serves, for the whole life of the process. Stdout belongs to the handshake line, so the log is the only place the backend can say anything
  • Analysis text reports: team-analysis-{project}-{timestamp}.log in logs/analysis/ — a hand-written product artifact from team_profile_exporter, not a logging handler

Rules:

  • Log level: LOG_LEVEL env var (DEBUG/INFO/WARNING/ERROR, default WARNING) — settable via .env or the Settings page Log Level cycle button (config.set_log_level() + apply_level())
  • Never log in per-frame code: _build_*_screen builders and render paths run every frame (~60 fps); logger.info belongs in key-handling branches of runner loops and one-shot functions only
  • INFO = user actions / page open-close / generate / export / config changes; DEBUG = action-time detail; WARNING/ERROR = every failure path. Never log secrets, tokens, join codes, or user content — log ids, counts, names, paths
  • All paths defined in src/yeaboi/paths.py — never hardcode Path.home() / ".yeaboi"
  • LangSmith 429 rate-limit errors are auto-suppressed via a custom logging filter in __init__.py
  • Token usage is tracked via track_usage() in agent/llm.py and persisted to token_usage table in SQLite

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.