Add Learning

Add a learning to the persistent SQLite database at ~/.kramme-cc-workflow/learnings.db.

$ARGUMENTS

Database Setup

First, ensure the database exists:

DB_FILE="$HOME/.kramme-cc-workflow/learnings.db"
if [ ! -f "$DB_FILE" ]; then
    bash "${CLAUDE_PLUGIN_ROOT}/scripts/init-learnings-db.sh"
fi

Categories

Collect Learning

Quick Mode (arguments provided)

Parse arguments:

• •First non-flag argument is the rule
• •--category or -c: category name
• •--project or -p: project name (defaults to current git repo name)
• •--mistake or -m: what went wrong

Example: /kramme:learn "Always check for null" --category Quality

Interactive Mode (no arguments)

Ask the user:

1. •"What did you learn? (the rule or insight)"
2. •"Which category?" (show options)
3. •"What mistake led to this?" (optional)

Sanitize Inputs

Before inserting, escape single quotes to avoid breaking SQL strings:

source "${CLAUDE_PLUGIN_ROOT}/scripts/learnings-sql.sh"

RULE_SAFE=$(sql_escape "$RULE")
CATEGORY_SAFE=$(sql_escape "$CATEGORY")
PROJECT_SAFE=$(sql_escape "$PROJECT")
MISTAKE_SAFE=$(sql_escape "$MISTAKE")

Insert Learning

sqlite3 "$HOME/.kramme-cc-workflow/learnings.db" \
  "INSERT INTO learnings (category, rule, mistake, project)
   VALUES ('$CATEGORY_SAFE', '$RULE_SAFE', '$MISTAKE_SAFE', '$PROJECT_SAFE')"

Use the *_SAFE variables in SQL strings.

Confirm:

Learning added to database (ID: N)
Category: $CATEGORY

Propose AGENTS.md Addition

After saving to the database, evaluate if this learning is project-specific (not a general best practice):

Add to AGENTS.md if:

• •References specific files, directories, or modules in this project
• •Describes project-specific quirks or conventions
• •Documents hidden dependencies or relationships in this codebase
• •Explains non-obvious build/test commands for this project

Skip AGENTS.md if:

• •General programming best practice
• •Language/framework knowledge applicable anywhere
• •Personal workflow preference

If project-relevant, propose:

question: "This learning seems specific to this project. Add to AGENTS.md?"
options:
  - label: "Yes, add to AGENTS.md"
    description: "Make this available in project context"
  - label: "No, database only"
    description: "Keep it searchable but not in project files"

Formatting for AGENTS.md

If user accepts, format the learning for AGENTS.md:

Guidelines:

• •Use short bullet points (1-2 lines)
• •Be direct and factual, no explanations
• •Use imperative mood ("Run X before Y", not "You should run X")
• •Include file paths or commands if relevant

Transform the learning:

Determine target file:

1. •Check if AGENTS.md exists in project root → use it
2. •Otherwise, check if CLAUDE.md exists → use it
3. •If neither exists, prefer AGENTS.md (it's designed for learnings)

Determine placement within file:

1. •Read the file and identify existing sections
2. •Find the most appropriate section based on category:
   • •Testing learnings → after "## Testing" or "## Tests" section
   • •Architecture learnings → after "## Architecture" or "## Structure" section
   • •Git learnings → after "## Git" or "## Workflow" section
   • •Otherwise → at end of file, or create a "## Learnings" section
3. •If no sections exist, append at end of file

Present the proposed addition:

**Proposed addition to AGENTS.md:**

```markdown
- [the formatted learning]

Placement: [End of file | After "## Build" section | etc.]

Ask for confirmation, then apply with Edit tool.

## Summary

Learning saved:

• •Database: ✓ (ID: N, searchable via /kramme:search-learnings)
• •AGENTS.md: ✓ Added | ✗ Skipped (not project-specific)