detailed-log

Adds prefixed debug logs to code and commits changes to Git.

Updated Jun 11, 2026
One-click install
npx skills add https://github.com/marcocpt/trae_skills --skill detailed-log-marcocpt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: detailed-log
Source: https://github.com/marcocpt/trae_skills/tree/main/detailed-log
Command: npx skills add https://github.com/marcocpt/trae_skills --skill detailed-log-marcocpt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Debugging issues in production or remote environments is hard when code lacks sufficient logging. This Skill instruments your code with structured debug logs tagged by a feature number prefix (e.g. [F1.10]), so you can quickly filter and locate relevant log lines during troubleshooting. ## Core Features & Use Cases - Feature-prefixed logging: Adds logs in a consistent format [feature-id] LEVEL | location | message | context across Swift, TypeScript/JavaScript, Python, and Kotlin/Java. - Standards-aware: Searches the project for coding_standards.md or similar guideline files and follows the project's own logging conventions when they exist. - Automatic Git commit: After adding logs, stages only the modified files and creates a conventional commit like feat(F1.10): add detailed debug logs, running SwiftLint first for Swift projects. - Use Case: You are debugging a data-fetching issue tagged as feature F1.10. Ask the AI to add detailed logs to the fetch module, and it instruments function entries, branches, async operations, and error handlers with prefixed log lines, then commits the changes locally. ## Quick Start Add detailed debug logs with the F1.10 prefix to my data request module and commit the changes.

Frequently Asked Questions about detailed-log

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

FAQPage Schema
How do I add debug logs with a feature tag prefix to my code?

Specify a feature number like F1.10 and the target file or function. The Skill inserts logs in the format [F1.10] LEVEL | location | message | context at function entries, branches, async operations, and error handlers.

What log format and levels does detailed logging use?

Logs follow the pattern [feature-id] LEVEL | location | message | context data. Levels are DEBUG for execution flow, INFO for key business nodes, WARN for recoverable issues, and ERROR for failures and exceptions.

Does it support Swift, Python, TypeScript, and Kotlin logging?

Yes, it provides logging examples for Swift (print), TypeScript/JavaScript (console.log), Python (logging module), and Kotlin/Java (Log.d/Log.e). If the project already uses a logging framework, that framework is used instead.

Will it follow my project's existing coding standards for logging?

Yes. Before adding logs it searches the project for coding_standards.md or similar guideline files and follows any defined log format, levels, or tooling. Project rules take priority over the default format.

Does it commit the logging changes to Git automatically?

Yes. It stages only the modified files and creates a local commit like feat(F1.10): add detailed debug logs. For Swift projects it runs SwiftLint first. It never pushes to a remote.

What should I avoid when adding debug logs to hot code paths?

Avoid logging inside high-frequency loops and never output sensitive data such as passwords, tokens, or personal information. Keep log volume moderate while including enough context for remote debugging.