aha

Captures repository context, recent commits, and decisions into a daily aha log.

16|9|Updated Apr 4, 2026
One-click install
npx skills add https://github.com/sonthanh/brain-os-plugin --skill aha
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aha
Source: https://github.com/sonthanh/brain-os-plugin/tree/main/skills/aha
Command: npx skills add https://github.com/sonthanh/brain-os-plugin --skill aha

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Capture key moments mid-session with full context to prevent losing important decisions or insights.

Core Features & Use Cases

  • Automatic context capture: repository, recent commits, and diffs to anchor moments
  • Daily logging: appends to the vault's daily aha log with timestamp and context
  • Non-intrusive: operates in the background and asks no questions when capturing
  • Use Case: while coding, say aha to capture a pivotal decision and its context for later review

Quick Start

Trigger /aha or say aha to capture the current moment and append it to your daily aha log.

Frequently Asked Questions about aha

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

FAQPage Schema
How do I capture key coding decisions and context without interrupting my workflow?

You can capture key decisions with full context by triggering the aha command, which instantly logs repository state, recent commits, and diffs into a daily file without prompting. It operates in the background to prevent losing important insights.

What is automatic context capture for daily journaling and how does it work?

Automatic context capture for daily journaling aggregates your current repository state, recent commits, and diffs when triggered, appending them with a timestamp to a daily log file. This anchors your moment with full technical context for later review.

Does the daily log capture require any manual input or configuration to work?

The daily log capture requires no manual input or configuration, operating with fast, no-questions capture. When you trigger the command, it immediately writes the current context and decisions to the vault's daily aha log without prompting.

What's the best way to log mid-session insights for later code review?

The best way to log mid-session insights is to trigger a non-intrusive capture that automatically aggregates repository context and recent commits. This fast, background approach writes directly to a daily file, preserving the moment without breaking your focus.

When do I need to capture repository context and diffs during a coding session?

You need to capture repository context and diffs when you make a pivotal decision or reach an important insight mid-session. Triggering the capture at that exact moment anchors the thought with full technical context for later review.

Can I review the captured moments and daily logs after my coding session ends?

You can review captured moments after your session by opening the daily aha log file in your vault. The log contains timestamped entries with aggregated repository context, recent commits, and your decisions appended throughout the day.