skills.rest
exception-coder
exception-coderCOMMUNITY
Explore all skills by this author →
GitHub

dev-log

Append timestamped development log entries to docs/dev-log/YYYY-MM-DD.md.

6|1|Updated Mar 30, 2026
Search Tags:#git#audit#traceability#docs#developer-workflow#dev-log#change-log
One-click install
npx skills add https://github.com/exception-coder/team-standards --skill dev-log-exception-coder
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dev-log
Source: https://github.com/exception-coder/team-standards/tree/main/skills/dev-log
Command: npx skills add https://github.com/exception-coder/team-standards --skill dev-log-exception-coder

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enforces consistent, timestamped recording of every change to the team-standards repository so reasons and impacts are preserved and traceable, preventing loss of context and easing audits.

Core Features & Use Cases

  • Mandatory daily logging: Appends all session changes to a single dated file under docs/dev-log/YYYY-MM-DD.md to centralize history.
  • Structured entries: Each entry includes time, change type, reason, detailed change list, and affected components for clear traceability.
  • Use case: When a Skill or configuration is added or modified during development, invoke this Skill to capture why the change was made and which Skills or docs it affects.

Quick Start

Invoke the dev-log Skill and append today's change to docs/dev-log/YYYY-MM-DD.md with a timestamp, change type, reason, list of modifications, and impact.

Frequently Asked Questions about dev-log

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

FAQPage Schema
How do I record and justify changes to team-standards files for traceability?▼

To record team-standards changes for traceability, append a structured entry to a dated markdown file under docs/dev-log/YYYY-MM-DD.md. Each log entry must include a timestamp, change type, reason, detailed change list, and impact section to preserve context.

What is the best way to maintain a development log for repository configuration changes?▼

Maintaining a development log for repository configurations requires appending all session changes to a centralized daily file. This ensures every modification to skills or configuration files is captured with a timestamp, change type, and detailed impact analysis for auditing.

How do I append a timestamped change log entry to a dated markdown file?▼

Appending a timestamped change log entry involves adding a structured markdown block to docs/dev-log/YYYY-MM-DD.md. You must document the time, change type, reason, list of modifications, and affected components to ensure complete traceability of the session.

Does a development log entry require an impact section for auditing?▼

Yes, a development log entry requires an impact section for auditing. Structured entries must include the time, change type, reason, detailed change list, and the specific impact to ensure repository changes are fully traceable and context is preserved.

When should I generate a dev log entry for modified skills?▼

You should generate a dev log entry for modified skills before ending a development session. Apply this logging process whenever skills, configuration, or repository files are added, modified, or deleted to capture the exact reasons and impacts of the changes.

Can I use a daily markdown file to centralize my team's development history?▼

Yes, you can use a daily markdown file to centralize your team's development history. The logging process appends all session changes to a single dated file under docs/dev-log/YYYY-MM-DD.md, preventing loss of context and easing repository audits.

Related Skills

Explore More Software Engineering Skills→
YehudaFrankelYehudaFrankel
16

learn

Extract reusable patterns, lessons, and decisions from the current session into memory files.

Community
Advanced
xiaoquqixiaoquqi

task-management

Automate task tracking with per-task Markdown files and a four-state lifecycle.

Community
Advanced
awinogradovawinogradov
5

pr:monitor

Monitor pull requests for review approval and CI check status.

Community
Intermediate
ysoftmanysoftman
9

commit

Review changes, lint/format files, and create an English commit message.

Community
Intermediate