Run a structured weekly review covering projects, habits, goals, and planning. Use when asked for a weekly review, week summary, or weekly planning session.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
Help Espen reflect on the past week and plan the next one. Covers professional projects, personal development, health, and learning goals.
Read recent activity to build a picture of the week:
# Recent daily notes (last 7)
VAULT="/Users/espen/Library/CloudStorage/OneDrive-Espennilsen.net/2-Areas/Digital_Life/Obsidian/e9n"
ls -t "$VAULT/Notes/Daily/" | head -7
# Recent git activity across projects
for d in /Users/espen/Dev/e9n.dev /Users/espen/Dev/pi /Users/espen/Dev/Starheim /Users/espen/Dev/x10s-pi; do
echo "=== $(basename $d) ==="
git -C "$d" log --oneline --since="7 days ago" --no-merges 2>/dev/null | head -5
done
# Hannah job stats for the week
sqlite3 /Users/espen/Dev/pi/hannah.db "
SELECT COUNT(*) as jobs, printf('\$%.4f', SUM(cost_total)) as cost, SUM(total_tokens) as tokens
FROM jobs WHERE created_at >= datetime('now', '-7 days');
"
Present findings organized as:
🏆 Wins — What went well, what was accomplished 📋 Active Projects — Status of each active project, progress this week 🎯 Goals Check-in — Health, learning, personal development progress ⚡ Blockers — What's stuck and why 📅 Next Week — Top 3 priorities, scheduled commitments, experiments to try
After presenting the review, ask:
If Espen wants, create a weekly review note in the vault:
Weekly Reviews/YYYY-WNN Review.md
Always confirm before writing to the vault.
Supportive but honest. Celebrate wins. Don't sugarcoat missed goals — frame them as data for adjustment, not failure. Channel stoic philosophy: focus on what's within control, let go of what isn't.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Audit, generate, update, and lint AGENTS.md files across all projects. Use when asked to check project context files, scaffold AGENTS.md for new projects, update stale ones, or run a cross-project audit.
The English summary is being prepared. Showing the original description.
Draft, edit, and publish blog posts for e9n.dev. Use when creating new posts, editing drafts, or refining existing content. Handles Eleventy frontmatter, Tailwind formatting, and Espen's authentic voice.
The English summary is being prepared. Showing the original description.
Generate a full operational status report for the Aivena bot. Checks all subsystems: extensions, webserver, Telegram, chat bridge, heartbeat, cron, database, memory, CRM, calendar, task management, jobs/telemetry, and storage. **Triggers — use this skill when:** - User asks for "status", "bot status", "system status", "operational status" - User asks "is everything running?", "how's Aivena doing?" - User says "health check", "diagnostics", "systems check" - User asks "what's the state of the bot?"
The English summary is being prepared. Showing the original description.
Parse git history and produce or update a CHANGELOG.md following the Keep a Changelog convention. Supports Conventional Commits, basic prefix conventions, and unstructured commit messages. Intelligently categorizes changes, detects breaking changes, links to PRs/issues, and handles both initial generation and incremental updates. **Triggers — use this skill when:** - User asks to "generate", "create", "update", or "write" a changelog - User mentions "CHANGELOG", "changelog", "release notes" - User says "document changes", "what changed since last release" - User wants to "prepare a release" and needs a changelog entry - User asks to "clean up" or "reformat" an existing changelog **Covers:** Any git-based project. Handles Conventional Commits (feat/fix/chore), Angular convention, basic prefixes (Add/Fix/Remove), and freeform commit messages. Outputs Keep a Changelog format with optional Common Changelog enhancements.
The English summary is being prepared. Showing the original description.
Orchestrate cmux terminal panes — split terminals, run parallel processes, read output from other panes, and use the built-in browser. Use when working inside cmux and you need to run a dev server, watch tests, spawn sub-agents, or preview web pages.
The English summary is being prepared. Showing the original description.
Review code for quality, security, performance, and maintainability. Use when reviewing PRs, auditing a codebase, or refactoring. Covers TypeScript, Node.js, infrastructure-as-code, and full-stack web apps.
The English summary is being prepared. Showing the original description.