skills.rest
samdae
samdaeCOMMUNITY
Explore all skills by this author →
GitHub

Trace

Record bug fixes and analysis results into structured trace logs.

1|Updated Jan 30, 2026
Search Tags:#changelog#documentation#audit#trace#traceability#software-development#bug-fix
One-click install
npx skills add https://github.com/samdae/archflow --skill trace-samdae
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Trace
Source: https://github.com/samdae/archflow/tree/main/skills/trace
Command: npx skills add https://github.com/samdae/archflow --skill trace-samdae

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps development teams maintain a clear, auditable record of bugs fixed, analysis performed, and design changes by producing a structured trace log.

Core Features & Use Cases

  • Automated trace entry creation after debugging sessions
  • Manual trace capture for ongoing investigations
  • Structured fields for Symptom, Cause, Action, and Impact to ensure traceability
  • Output stored at docs/{serviceName}/trace.md aligned with project documentation

Quick Start

  1. Trigger the trace workflow from a debug session or invoke Trace manually.
  2. Provide the service name and the result type (fix, external cause, investigation, or other changes).
  3. Fill in the required fields: Symptom, Cause, Action, and Impact.
  4. Review and save to docs/{serviceName}/trace.md.

Frequently Asked Questions about Trace

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

FAQPage Schema
How do I automate changelog recording after a debugging session?▼

Automated changelog recording triggers post-debug to capture bug fixes and analysis. It writes structured trace entries including symptoms, causes, actions, and impacts directly to docs/{serviceName}/trace.md.

What is a structured trace log for software development?▼

A structured trace log is an auditable record documenting bug fixes, analysis, and design changes. It ensures traceability by capturing specific fields: Symptom, Cause, Action, and Impact for every investigation.

Can I manually log ongoing investigations across multiple services?▼

Manual trace capture supports logging ongoing investigations across multiple services. You invoke the workflow manually, provide the service name and result type, then fill in the structured fields for traceability.

Does this traceability workflow integrate with existing project documentation?▼

Traceability integrates with project documentation by saving outputs to docs/{serviceName}/trace.md. This aligns the structured audit log of symptoms, causes, actions, and impacts directly within your existing docs.

What's the best way to maintain an auditable record of design impacts and bug fixes?▼

Maintaining an auditable record is best achieved through a centralized trace log. Documenting design impacts and bug fixes with structured fields ensures clear traceability for development teams.

What result types are supported when recording a trace entry?▼

Supported result types for recording a trace entry include fix, external cause, investigation, and other changes. You select the type during workflow invocation before inputting the required fields.

Related Skills

Explore More Software Engineering Skills→
maxthemanmaxtheman

trace-to-root

Trace debugging symptoms backward to root causes using HelixDB and Repo Prompt.

Community
Advanced
npownpow
4

monitor

Monitor operational targets and convert health signals into threshold-based status reports.

Community
Advanced
jjub0217jjub0217

learn-log

Parse session JSONL histories and append Q&A, insights, and action items to a Markdown weekly log.

Community
Intermediate
apexradiusapexradius

retro

Analyze git history, issues, and session logs to generate structured retrospectives.

Official
Intermediate