trace

Record bug fixes, design impacts, and code mapping changes into trace.md.

Updated Mar 7, 2026
One-click install
npx skills add https://github.com/Marunion/ai-factbomb --skill trace-marunion
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: trace
Source: https://github.com/Marunion/ai-factbomb/tree/main/archflow-main/skills/trace
Command: npx skills add https://github.com/Marunion/ai-factbomb --skill trace-marunion

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the process of recording bug fixes, design changes, and their impact, ensuring a clear and consistent changelog for software development.

Core Features & Use Cases

  • Automated Bug Fix Logging: Records details of bug fixes, including symptom, cause, and resolution.
  • Design Impact Tracking: Documents the impact of design changes on the system.
  • Code Mapping Updates: Integrates with arch.md to track structural code changes.
  • Use Case: After fixing a critical bug, use this Skill to automatically log the fix, its cause, and any related code mapping updates to the trace.md file, ensuring the team is always up-to-date.

Quick Start

Use the trace skill to record a bug fix for the user authentication service.

Frequently Asked Questions about trace

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

FAQPage Schema
How do I automatically log bug fixes and design impacts for my software project?

To log bug fixes and design impacts, you can trigger an automated recording process that extracts the symptom, cause, and fix content from debug sessions. It generates a detailed changelog entry and updates code mapping tables into a trace.md file.

What is the best way to maintain a changelog for code mapping modifications?

Maintaining a changelog for code mapping modifications involves recording structural changes by integrating with architecture files like arch.md. This documents the impact scope and updates mapping tables, ensuring the team tracks structural code changes consistently.

Does bug tracking and changelog generation require a specific development context to work?

Bug tracking and changelog generation requires a debug context to function properly. It supports all platforms and triggers through commands like trace, log, record, and changelog to extract information from active debug sessions or manual input.

Can I document the impact scope and root cause of a bug fix after a debug session?

You can document the impact scope and root cause by extracting information directly from debug sessions or manual input. The process records the symptom, cause, fix content, and impact scope to generate a comprehensive changelog entry.

How do code mapping updates integrate with changelog entries during version control?

Code mapping updates integrate with changelog entries by linking structural modifications to architecture documentation. The process extracts code mapping changes and updates the relevant tables, ensuring version control logs reflect both the bug resolution and system design impact.