What is the purpose of the trace.md file?

The trace.md file serves as a persistent record of all significant changes, including the reasoning behind fixes, their impact on the project architecture, and how they were verified.

Does this skill help with Git commit messages?

Yes, Trace provides a recommended commit message format following the 'docs({serviceName}): trace - {summary}' pattern to keep your repository history clean and informative.

How does the Trace skill work with the debug skill?

When a bug is fixed using the debug skill, Trace automatically extracts the symptom, cause, and fix details to generate a structured entry in your trace.md file without manual re-entry.

What are Code Mapping changes in the Trace skill?

Code Mapping changes are records of structural modifications—such as adding or deleting methods—that are staged in the changelog before being synchronized with your arch.md file.

Can I use Trace manually without a debugging session?

Yes, the skill is user-invocable. When called manually, it will prompt you through a series of questions to classify and record your changes or investigation results.

Trace - Automated Changelog & Impact Tracker

Name: Trace - Automated Changelog & Impact Tracker
Author: samdae

bysamdae

0•

Analytics & Monitoring

Records bug fixes, code modifications, and architectural impacts into a structured trace.md file to maintain project traceability.

The Trace skill is a specialized component of the Archflow document-driven development framework that automates the documentation of software changes. It bridges the gap between active development and architectural records by capturing the context of bug fixes, classifying result types, and mapping structural changes to a project's architecture. Whether triggered automatically after a debugging session or invoked manually, Trace ensures that every modification is documented with its root cause, impact scope, and verification steps, providing a high-fidelity audit trail for complex codebases.

Key Features

01Code Mapping tracking to identify structural changes in files, classes, and methods.

020 GitHub stars

03Result classification for code fixes, external causes, and ongoing investigations.

04Structured changelog generation in trace.md with severity and impact analysis.

05Integration with synchronization workflows to update project architecture documentation.

06Automated extraction of bug fix context and root cause analysis from debug sessions.

Use Cases

01Performing impact analysis by documenting direct and indirect consequences of code changes.

02Capturing root cause analysis and verification methods during a multi-agent debugging workflow.

03Maintaining an automated, detailed changelog that links specific fixes to architectural components.

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add samdae/archflow trace

For use in Claude.ai and ChatGPT

Download Skill