aidd-log

Create structured changelogs for completed epics with emoji categorization.

377|33|Updated Jul 3, 2025
One-click install
npx skills add https://github.com/paralleldrive/aidd --skill aidd-log
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aidd-log
Source: https://github.com/paralleldrive/aidd/tree/main/ai/skills/aidd-log
Command: npx skills add https://github.com/paralleldrive/aidd --skill aidd-log

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, bash, and includes scripts (resource) components.

What problem does it solve?

This Skill simplifies project history documentation by automating the creation of a structured changelog with emoji categorization for completed epics.

Core Features & Use Cases

  • Epic Logging: Automates the logging of completed epics after significant feature or epic completions.
  • Changelog Structure: Generates a consistent, easy-to-scan changelog with emoji categorization.
  • Use Case: After the completion of a major feature, use this Skill to log the epic in the changelog with a concise description and emoji to categorize its type.

Quick Start

After completing a significant feature or epic, invoke /aidd-log and follow the prompt to log the epic with its name and a brief description.

Frequently Asked Questions about aidd-log

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

FAQPage Schema
How do I automate changelog generation for completed project epics?

To automate changelog generation for project epics, invoke the aidd-log command after completing a feature. It logs the epic with a concise description and applies emoji categorization to maintain a consistent, scannable project history.

What is emoji categorization in a project changelog?

Emoji categorization in a changelog visually tags completed epics by type, making project history easy to scan. It automates structuring changelog entries so developers can quickly identify the nature of recent software development updates.

Do I need git and bash to log epics in a changelog?

Yes, you need both git and bash installed to log epics in the changelog. The Skill relies on these dependencies to execute its scripts and automate the history documentation process within your development environment.

When should I document project history with an automated changelog?

You should document project history with an automated changelog immediately after the completion of a major feature or epic. This ensures your development milestones are consistently recorded while context is fresh.

What's the best way to structure a changelog for software development epics?

The best way to structure a changelog for epics is using automated emoji categorization. This provides a consistent, scannable format for project history documentation, allowing teams to quickly identify completed features.

Can I use bash scripts to maintain changelog history documentation?

Yes, you can use bash scripts to maintain changelog history documentation. This Skill provides scripts that run in bash to automatically generate structured entries for completed epics, requiring git for operations.