git-aware-coding-agent: Skill for Cursor

Avos History

Use this skill when you need chronological history of a subject in the repository.

When to Use

Use this skill when at least one trigger applies:

• You are changing existing production behavior
• You are refactoring or touching shared/unfamiliar modules
• The change is medium/large (multi-file, broad behavior impact)
• You need to understand prior constraints before redesigning logic

You can skip for low-risk tasks:

• Docs/comments/typo-only edits
• New isolated files with no modification to existing behavior
• Test-only updates not affecting runtime behavior

Command

avos history --json "subject or topic"

Examples

Module History

avos history --json "authentication module"

Feature Evolution

avos history --json "user registration flow"

File History

avos history --json "database connection handling"

Response Format

Success with timeline:

{
  "success": true,
  "data": {
    "format": "avos.history.v1",
    "raw_text": "...",
    "timeline": {
      "is_empty_history": false,
      "months": [
        {
          "month": "2026-01",
          "events": [
            {
              "type": "pr",
              "ref": "123",
              "title": "Add JWT authentication",
              "author": "developer"
            }
          ]
        }
      ],
      "unparsed_timeline_lines": []
    },
    "summary": {
      "text": "The authentication module was introduced in January 2026..."
    },
    "parse_warnings": []
  }
}

No history found:

{
  "success": true,
  "data": {
    "format": "avos.history.v1",
    "timeline": {
      "is_empty_history": true,
      "months": []
    },
    "summary": {
      "text": "No engineering history found for \"subject\"."
    }
  }
}

Best Practices

1. Check history before modifying: Always understand the context before changing existing code
2. Use specific subjects: "payment processing" is better than "payments"
3. Review the timeline: Understand the evolution before making changes