context-add

# Add Context Commits

This skill guides you through creating new [CONTEXT] commits to document project knowledge and updating CLAUDE.md to reference them.

## When to Use

Use this skill when:
- Adding new project requirements or specifications
- Documenting a new workflow or process
- Recording architectural decisions
- Adding coding standards or conventions
- The user requests to "add context" or "document workflow"

## Steps to Add Context

### 1. Determine Context Type

Ask the user what type of context they want to add:
- **Requirements/Specifications**: Project goals, features, technical requirements
- **Workflows**: Development processes, TDD practices, deployment procedures
- **Architecture**: Design decisions, patterns, trade-offs, technical choices
- **Standards**: Coding conventions, style guides, best practices
- **Domain Knowledge**: Business logic, domain concepts, terminology

### 2. Create the [CONTEXT] Commit

Create an empty commit with [CONTEXT] prefix and detailed message:

```bash
git commit --allow-empty -m "[CONTEXT] Brief title here

Detailed explanation of the context.

## Section 1
- Point 1
- Point 2

## Section 2
- More details
- Guidelines
- Examples

## Notes
Additional information or rationale.
"
```

**Important**: Use `--allow-empty` to create documentation commits without file changes.

### 3. Get the Commit Hash

Retrieve the hash of the newly created commit:

```bash
git log -1 --format=%H
```

Or for abbreviated hash:

```bash
git log -1 --format=%h
```

### 4. Update CLAUDE.md

Read the current CLAUDE.md and add the new commit reference:

```bash
# Read current CLAUDE.md
cat CLAUDE.md
```

Add a new line to the context list with format:
```
 N. [commit-hash] Brief description
```

Maintain numbering sequence and keep context-progress as the last item.

### 5. Verify the Addition

Confirm the new context is accessible:

```bash
# Read the new context commit
git log [new-commit-hash] -1 --format=%B

# Verify CLAUDE.md updated
cat