DevTrail New Skill

Create DevTrail documentation based on recent changes.

Instructions

When invoked, follow these steps:

1. Check for Parameters

If the user specified a document type (e.g., /devtrail-new ailog), skip to step 4 using that type.

Valid types: ailog, aidec, adr, eth, req, tes, inc, tde

2. Analyze Context

Gather information about recent changes:

bash
1# Get current date
2date +%Y-%m-%d
3
4# Get modified files (staged and unstaged)
5git status --porcelain
6
7# Get recent changes summary
8git diff --stat HEAD~1 2>/dev/null || git diff --stat
9
10# Count lines changed
11git diff --numstat HEAD~1 2>/dev/null || git diff --numstat

3. Classify and Suggest Type

Based on the analysis, suggest a document type:

4. Confirm with User

Always display this confirmation before creating:

╔══════════════════════════════════════════════════════════════════╗
║  DevTrail New                                                    ║
╠══════════════════════════════════════════════════════════════════╣
║                                                                   ║
║  📊 Analysis:                                                     ║
║     • Files modified: [N]                                         ║
║     • Lines changed: [+X / -Y]                                    ║
║     • Area: [detected area or "general"]                          ║
║                                                                   ║
║  🎯 Suggested type: [TYPE] ([Full Name])                          ║
║     Reason: [Brief explanation]                                   ║
║                                                                   ║
║  📝 Proposed filename:                                            ║
║     [TYPE]-YYYY-MM-DD-NNN-[description].md                        ║
║                                                                   ║
╚══════════════════════════════════════════════════════════════════╝

Confirm creation? [Y/n/other type]:

Wait for user confirmation before proceeding.

5. Check Language Configuration

Read .devtrail/config.yml to determine language:

yaml
1language: en  # or es

Use template path based on language:

• en (default): .devtrail/templates/TEMPLATE-[TYPE].md
• es: .devtrail/templates/i18n/es/TEMPLATE-[TYPE].md

6. Generate Document ID

Determine the next sequence number:

bash
1# Find existing documents of this type for today
2ls .devtrail/*/[TYPE]-$(date +%Y-%m-%d)-*.md 2>/dev/null | wc -l

ID format: [TYPE]-YYYY-MM-DD-NNN

7. Load Template and Create Document

1. Read the appropriate template
2. Replace placeholders:
   • YYYY-MM-DD → Current date
   • NNN → Sequence number (001, 002, etc.)
   • [agent-name-v1.0] → gemini-cli-v1.0
3. Fill in context from git analysis
4. Save to correct location:

8. Report Result

After creation, display:

✅ DevTrail document created:
   .devtrail/[path]/[TYPE]-YYYY-MM-DD-NNN-description.md

   Review required: [yes/no]
   Risk level: [low/medium/high/critical]

Document Type Reference

Edge Cases

1. No git repository: Inform user that git is required for context analysis
2. No changes detected: Ask user to describe what to document
3. User declines: Acknowledge and exit gracefully
4. Invalid type parameter: Show valid types and ask again