Does it support external issue trackers?

It can detect indicators for GitHub, Linear, Jira, and Beads. While it can't always log in for you, it identifies when these trackers are present and can pull data via CLI tools like 'gh' or 'bd'.

Can this skill access my Claude chat history?

Yes, it is specifically designed to parse local Claude chat history files to identify key decisions and discussions that happened during the development process.

How does DevLog differ from a standard git log?

While a git log tracks specific code changes, DevLog captures the 'why' behind the project—the story, the decisions, the challenges, and the pivots—written in a narrative style that is easier for humans to read and understand.

Will large project histories break the skill?

No, the skill includes a specific workflow for 'Handling Large History Files' using iterative parsing and chunked reading to ensure it stays within context limits while gathering information.

DevLog Narrative Generator

Name: DevLog Narrative Generator
Author: jbdamask

byjbdamask

•

Learning & Documentation

Automates the creation and maintenance of a chronological development story for projects by capturing architectural decisions and pivots.

About

The DevLog skill helps developers maintain a living record of their project's journey within a DEVLOG.md file. Unlike standard changelogs, it synthesizes information from Git commits, Claude chat history, planning documents, and issue trackers to create a readable narrative of why certain decisions were made and how the project evolved. It is ideal for preserving context during long-term development, managing context switches, or providing a clear onboarding path for new contributors.

Key Features

1 GitHub stars
Chunked processing strategy for handling large history files without context overflow
Standardized project status tracking and purpose-driven descriptions
Automated extraction of architectural decisions, research findings, and project pivots
Chronological DEVLOG.md maintenance with narrative-driven entries
Multi-source analysis including Git logs, Claude chat history, and issue trackers

Use Cases

Summarizing project progress before taking a break or switching to a different project
Documenting major architectural shifts and the rationale behind technical debt
Creating an accessible project history for stakeholders or new team members

About

Key Features

1 GitHub stars
Chunked processing strategy for handling large history files without context overflow
Standardized project status tracking and purpose-driven descriptions
Automated extraction of architectural decisions, research findings, and project pivots
Chronological DEVLOG.md maintenance with narrative-driven entries
Multi-source analysis including Git logs, Claude chat history, and issue trackers

Use Cases

Summarizing project progress before taking a break or switching to a different project
Documenting major architectural shifts and the rationale behind technical debt
Creating an accessible project history for stakeholders or new team members