logger

Log development activities in YAML and generate Markdown session reports.

Updated Jan 26, 2023
One-click install
npx skills add https://github.com/avvale/aurora-back --skill logger-avvale
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: logger
Source: https://github.com/avvale/aurora-back/tree/main/.claude/skills/logger
Command: npx skills add https://github.com/avvale/aurora-back --skill logger-avvale

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a structured way to log development activities, track progress, and automatically generate comprehensive session reports, improving visibility and traceability in development work.

Core Features & Use Cases

  • Structured Activity Logging: Log tasks, skills applied, files modified, and complexity in a standardized format.
  • Automated Report Generation: Compile logs into detailed Markdown reports summarizing work done, architectural decisions, and metrics.
  • Use Case: After completing a feature, log the details of the implementation, testing, and any architectural decisions made. Then, generate a session report to document your work and optionally save it for future reference.

Quick Start

Log your completed development activity using the provided YAML format.

Frequently Asked Questions about logger

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I track development activities for a session report?

Track development activities by logging tasks, skills applied, files modified, and complexity in a structured YAML format, which is then compiled into a comprehensive session report.

What is the best way to log architectural decisions and tasks during development?

The best way to log architectural decisions is using a defined YAML protocol that records implementation details, testing, and complexity to generate traceable Markdown session reports.

How do I generate a Markdown summary of my development work?

Generate a Markdown summary of development work by compiling structured YAML logs of tasks and files modified into automated, comprehensive session reports for documentation.

Can I use a YAML format to log modified files and task complexity?

Yes, you can use a standardized YAML format to log modified files, task complexity, and applied skills, enabling automated compilation into detailed session reports.

Why do I need structured logging for development traceability?

Structured logging is needed for development traceability to create audit trails, facilitate learning from past sessions, and provide visibility into architectural decisions and progress.

Does structured activity logging work without external dependencies?

Structured activity logging works without external dependencies by relying on a defined YAML protocol to capture development metrics and generate comprehensive Markdown reports.