Record what was accomplished in a development session. This creates the project's memory — not Claude's memory (that's MEMORY.md), but a human-readable record of what happened and why.

Storage

Devlog entries go in docs/devlog/YYYY-MM.md (one file per month)
Each entry is a date-headed section within the monthly file

Process

When invoked (/devlog):

Gather context automatically — do NOT ask the user what happened. Instead:
- Run git log --oneline --since="6am" --author to find today's commits
- Run git diff --stat HEAD~5 to understand scope of recent changes
- Review the current conversation for decisions made, problems solved, and discoveries
- Check if any ADRs were created today
Create/append the entry in docs/devlog/YYYY-MM.md:
- If the file doesn't exist, create it with a # Development Log — YYYY-MM header
- Append a new section for today's date
Write the entry using this format:

## YYYY-MM-DD

### [Primary Topic]
- What was done (1-3 bullets, concise)
- Key decision or discovery
- See: [link to ADR, doc, or file if relevant]

### [Secondary Topic] (if applicable)
- ...

Keep it brief — 3-10 lines per topic. This is a log, not a report.

What to Include

Features implemented or bugs fixed
Architecture decisions made (link to ADR if created)
Problems discovered and how they were resolved
Refactoring done and why
New patterns established
Research findings that affected the project

What NOT to Include

Step-by-step implementation details (that's in git history)
Full code snippets (link to files instead)
Speculative future plans (that's backlog)
Routine maintenance (dependency updates, formatting)

Example Entry

## 2026-02-21

### MNET Income Data — Business Day Resolution
- Discovered `tbCenterIncomeTotal` only has data through last business day (unlike `tbFinalTotal` which is real-time)
- Added `Mnet.run_date/1` using `mng.tbRunCalendar` to resolve any date to its business day
- See: ADR-0003, `docs/infrastructure/mnet-running-status.md` §14

### AI System Prompt Refactoring
- Split monolithic `build_system_prompt/2` into 7 composable functions
- Added Data Resolution Strategy section to guide LLM on schema exploration
- See: `lib/gs_net/ai/chat.ex`

Más de este repositorio

mismo repositorio

adr

jhlee111/ash_feedback

Create or manage Architecture Decision Records (ADRs) in docs/decisions/

2026-04-210

ash-framework

jhlee111/ash_feedback

Use this skill working with Ash Framework or any of its extensions. Always consult this when making any domain changes, features or fixes.

2026-04-210

e2e-test

jhlee111/ash_feedback

Run E2E browser tests via Tidewave browser_eval against the running Phoenix dev server

2026-04-210

lv-inspect

jhlee111/ash_feedback

Inspect LiveView state (assigns, components) via Phoenix.LiveView.Debug in project_eval

2026-04-210

pickup

jhlee111/ash_feedback

Morning briefing — where we left off, what to work on today. Fast, compact report from canonical sources.

2026-04-210

plan-status

jhlee111/ash_feedback

Manage plan lifecycle — list plans, mark completed/abandoned, move between directories

2026-04-210

Development Log

Record what was accomplished in a development session. This creates the project's memory — not Claude's memory (that's MEMORY.md), but a human-readable record of what happened and why.

Storage

Devlog entries go in docs/devlog/YYYY-MM.md (one file per month)

Each entry is a date-headed section within the monthly file

Process

When invoked (/devlog):

Gather context automatically — do NOT ask the user what happened. Instead:

Run git log --oneline --since="6am" --author to find today's commits
Run git diff --stat HEAD~5 to understand scope of recent changes
Review the current conversation for decisions made, problems solved, and discoveries
Check if any ADRs were created today

Create/append the entry in docs/devlog/YYYY-MM.md:

If the file doesn't exist, create it with a # Development Log — YYYY-MM header
Append a new section for today's date

Write the entry using this format:

## YYYY-MM-DD ### [Primary Topic] - What was done (1-3 bullets, concise) - Key decision or discovery - See: [link to ADR, doc, or file if relevant] ### [Secondary Topic] (if applicable) - ...

Keep it brief — 3-10 lines per topic. This is a log, not a report.

What to Include

Features implemented or bugs fixed

Architecture decisions made (link to ADR if created)

Problems discovered and how they were resolved

Refactoring done and why

New patterns established

Research findings that affected the project

What NOT to Include

Step-by-step implementation details (that's in git history)

Full code snippets (link to files instead)

Speculative future plans (that's backlog)

Routine maintenance (dependency updates, formatting)

Example Entry

## 2026-02-21 ### MNET Income Data — Business Day Resolution - Discovered `tbCenterIncomeTotal` only has data through last business day (unlike `tbFinalTotal` which is real-time) - Added `Mnet.run_date/1` using `mng.tbRunCalendar` to resolve any date to its business day - See: ADR-0003, `docs/infrastructure/mnet-running-status.md` §14 ### AI System Prompt Refactoring - Split monolithic `build_system_prompt/2` into 7 composable functions - Added Data Resolution Strategy section to guide LLM on schema exploration - See: `lib/gs_net/ai/chat.ex`