# devtrail-status

> Show DevTrail documentation status. Use to verify if AI agents properly documented their changes.

- Author: Jose Villaseñor Montfort
- Repository: Enigmora/devtrail
- Version: 20260129195547
- Stars: 1
- Forks: 0
- Last Updated: 2026-02-06
- Source: https://github.com/Enigmora/devtrail
- Web: https://mule.run/skillshub/@@Enigmora/devtrail~devtrail-status:20260129195547

---

---
name: devtrail-status
description: Show DevTrail documentation status. Use to verify if AI agents properly documented their changes.
allowed-tools: Read, Glob, Bash(git diff *, git log *, git status *, date *)
---

# DevTrail Status Skill

This skill checks the documentation status of the DevTrail in the current project.

## Instructions

When invoked, perform the following checks and display the results:

### 1. Find Recent DevTrail Documents

Search for DevTrail documents created or modified in the last hour:

```bash
# Get documents modified in the last hour
git log --since="1 hour ago" --name-only --pretty=format: -- ".devtrail/**/*.md" | sort -u | grep -v "^$"
```

If git is not available or the directory is not a git repo, use file modification times:
- Check `.devtrail/07-ai-audit/agent-logs/` for recent AILOG files
- Check `.devtrail/07-ai-audit/decisions/` for recent AIDEC files
- Check `.devtrail/07-ai-audit/ethical-reviews/` for recent ETH files

### 2. Find Modified Source Files

Identify source files that were modified and might need documentation:

```bash
# Get modified files (staged and unstaged)
git diff --name-only HEAD~1..HEAD 2>/dev/null || git diff --name-only
```

Filter to show only files that might need documentation:
- Exclude: `*.md`, `*.json`, `*.yml`, `*.yaml`, `*.lock`, `package-lock.json`
- Include: `*.ts`, `*.js`, `*.tsx`, `*.jsx`, `*.py`, `*.go`, `*.rs`, `*.java`, `*.cs`, `*.rb`, `*.php`

### 3. Analyze Documentation Gaps

For each modified source file, check if there's a corresponding DevTrail document:
- Files with >10 lines of changes in business logic folders should have an AILOG
- Security-related files should have documentation with `risk_level: high`

### 4. Display Results

Format the output as follows:

```
DevTrail Status
================================================================================

Recent Documents (last hour):
  [checkmark] AILOG-2025-01-27-001-implement-auth.md
  [checkmark] AIDEC-2025-01-27-001-auth-strategy.md

Modified Files Without Documentation:
  [warning] src/auth/login.ts (47 lines changed)
  [warning] src/api/users.ts (23 lines changed)

Summary:
  Documents created: 2
  Files needing review: 2

Use /devtrail-status after making changes to verify documentation compliance.
```

### Symbol Legend

- `[checkmark]` = Documentation exists (use checkmark symbol)
- `[warning]` = May need documentation (use warning symbol)
- `[info]` = Informational (use info symbol)

### Edge Cases

1. **No git repository**: Show message explaining git is required for full functionality
2. **No recent documents**: Show "No DevTrail documents created in the last hour"
3. **No modified files**: Show "No source files modified recently"
4. **Empty .devtrail directory**: Show warning that DevTrail may not be properly set up

### Additional Notes

- This skill is read-only and does not create or modify files
- Run this after completing development tasks to verify documentation compliance
- If files need documentation, remind the user of the DevTrail rules