From dev-log
Automatically log development sessions - captures tools, decisions, accounts, and progress from conversation context
How this skill is triggered — by the user, by Claude, or both
Slash command
/dev-log:dev-logThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Automatically captures development work from conversation context. One file per project with timestamped entries. No questions asked - just run `/dev-log` and it extracts everything.
Automatically captures development work from conversation context. One file per project with timestamped entries. No questions asked - just run /dev-log and it extracts everything.
Root: ~/dev-log/ (configurable)
When you first run /dev-log, if the directory doesn't exist, you'll be asked:
"Where would you like to store development logs?"
Options:
~/dev-log/) - Recommended for personal use across all projects./.dev-log/) - Keep logs within project directoryYour choice is saved to .claude/dev-log.local.md in the current project.
dev-log/
├── projects/
│ ├── clawdbot.md # All clawdbot work
│ ├── dev-log.md # This skill's development
│ └── <project>.md # One file per project
├── drafts/ # Content creation outputs
└── index.json # Project metadata
| Command | Action |
|---|---|
/dev-log | Auto-capture session to detected project |
/dev-log <project> | Auto-capture to specific project |
/dev-log show | View current project entries |
/dev-log show <project> | View specific project entries |
/dev-log list | List all projects |
/dev-log interview | 12-question content capture (for publishing) |
/dev-log content | Generate content from existing logs |
/dev-log drafts | List content drafts |
/dev-log help | Show detailed help |
Running /dev-log automatically extracts from conversation:
No questions asked. Just analyzes the conversation and logs.
Use /dev-log interview ONLY when you want to create publishable content.
Generates:
Auto-detects from:
Override: /dev-log my-project-name
## 2026-01-15 18:26 AEDT
### Summary
Set up Clawdbot with Tailscale Funnel for Gmail webhooks...
### Decisions Made
- **Tailscale over ngrok**: Persistent URL, no signup...
### Tools & SDKs
| Tool | Purpose | Notes |
|------|---------|-------|
| Tailscale | Public HTTPS | Funnel enabled |
### Next Steps
- [ ] Auth ElevenLabs CLI
npx claudepluginhub imehr/imehr-marketplace --plugin dev-logLogs accomplishments from Claude Code sessions to dated markdown files at session end, context checkpoints, self-improve triggers, or user request.
Logs session accomplishments, file changes, commits, decisions, and next steps for future recall. Triggered by phrases like 'save diary' or 'wrapping up'.
Generates markdown developer journals from Claude Code activity data over specified time periods like today or last week. Focuses on accomplishments, decisions, and project progress with day-by-day breakdowns.