remi

Category: Tools & Productivity | Uploader: ogxd | Downloads: 0 | Version: v1.0（Latest）

This skill provides a work history. Always use this skill before answering any question that involves what the user has worked on, built, shipped, or contributed to — at any level of granularity or time range. Do not attempt to answer from memory or context alone; the data lives on disk and must be queried.

Changelog: Source: GitHub https://github.com/ogxd/remi

Directory Structure

Current level: Root

📁 .github/
- 📁 workflows/
  - 📄 release.yml 14.1 KB
📁 src/
- 📄 git.rs 3.2 KB
- 📄 hook.rs 2.5 KB
- 📄 journal.rs 834 B
- 📄 main.rs 4.2 KB
- 📄 paths.rs 656 B
- 📄 pending.rs 8.9 KB
- 📄 recap.rs 5.8 KB
- 📄 scan.rs 2.8 KB
📄 .gitignore 7 B
📄 Cargo.lock 10.8 KB
📄 Cargo.toml 427 B
📄 dist-workspace.toml 571 B
📄 LICENSE.md 33.5 KB
📄 README.md 2.2 KB
📄 rustfmt.toml 16 B
📄 SKILL.md 4.6 KB

SKILL.md

---
name: remi
description: This skill provides a work history. Always use this skill before answering any question that involves what the user has worked on, built, shipped, or contributed to — at any level of granularity or time range. Do not attempt to answer from memory or context alone; the data lives on disk and must be queried.
---

Trigger on any phrasing that implies knowledge of past work. Here are some examples of requests that require this skill — and anything similar:

**Engineering**
- "Look for optimizations in [repository], skipping anything I've already tried."
- "When might that [regression] have been introduced?"
- "Summarize my contributions to [project]."
- "Tell me when I last worked on [project] and for how long."

**Reporting & Admin**
- "Prepare my weekly meeting notes."
- "Fill my time sheets for the past two weeks."
- "Give me peer feedback on my work, as if your were my colleague."
- "How's my productivity going?"

**Career & Growth**
- "Identify key areas to improve my overall productivity."
- "Write my self-assessment and performance review."
- "Track my technical progression since I joined the company."
- "What's my coding style like?"

## Step 1 — Ensure the correct version of remi is installed

This skill requires **remi 0.2.3**. Check the installed version:

```sh
remi --version
```

If the command is not found or the version is not `remi 0.2.3`, install the exact required version:

```sh
curl --proto '=https' --tlsv1.2 -LsSf https://github.com/ogxd/remi/releases/download/v0.2.3/remi-installer.sh | sh
```

## Step 2 — Initialize the database (first time only)

Check whether `~/.remi/` contains any year directories:

```sh
ls ~/.remi/ 2>/dev/null | grep -E '^[0-9]{4}$'
```

If no year directories are found, the database has never been populated. **Ask the user** which directory contains their git repositories (e.g. `~/src`, `~/projects`), then scan it:

```sh
remi scan <path>
```

A date range can be provided to limit scope:

```sh
remi scan <path> --start 2025-01-01
```

This step is only needed once. After that, the git hook keeps the database up to date automatically.

## Step 3 — Run `remi check`

`remi check` is the ongoing agent command. It installs the git hook (if not already done), queues recap jobs for any past periods that are missing one, and outputs all pending items.

```sh
remi check
```

`remi check` outputs all pending items to stdout. Process each item using a subagent (to keep the main context clean):

**For each pending commit:**
1. Read the diff from the `remi check` output
2. Summarize it in one concise sentence
3. Call: `remi record commit <hash> "<summary>"`

**For each pending recap:**
1. Read the log content from the `remi check` output
2. Generate a recap in markdown (bullet points, key themes, notable achievements)
3. Write the recap directly to the output path shown
4. Call: `remi record recap <period>`

Process month recaps before year recaps, since year recaps may draw from monthly recap files.

## How the data is organized

All data lives under `~/.remi/`:

```
~/.remi/
  pending/
    abc1234.md        ← pending commit (written by hook or scan)
    recap-2025-01.md  ← pending month recap
    recap-2025.md     ← pending year recap
  2025/
    01/
      recap.md        ← monthly recap (written by agent)
      14-01-2025.md   ← daily log
      27-01-2025.md
    ...
    recap.md          ← yearly recap (written by agent)
  2026/
    03/
      07-03-2026.md
  remi.log
```

Each daily log contains one entry per commit:

```markdown
- [14:32:10] Commit a3f9c12 on repository "my-project"
  - Message: Fix null pointer in auth handler
  - Description: Adds a nil check before dereferencing the user pointer in the auth middleware.
```

## How to query the database efficiently

The data is structured for progressive summarization. Always start from the coarsest level and drill down only as needed — this keeps the context window small.

**For a broad question (e.g. "what did I work on in 2025?"):**
Read the yearly recap first: `~/.remi/2025/recap.md`

**For a monthly question (e.g. "what did I ship in January?"):**
Read the monthly recap: `~/.remi/2025/01/recap.md`

**For a specific week or day:**
Read the relevant daily log files directly, e.g. `~/.remi/2026/03/07-03-2026.md`

**For a question spanning multiple months:**
Read monthly recaps one by one, and only open daily logs if more detail is needed on a specific period.

Never load all daily logs at once — recaps exist precisely to avoid that. Only drill into daily logs when the question requires commit-level detail or when a recap does not exist yet for a period.

Comments 0

Latest | Hot

Please login before commenting.

No comments yet. Be the first one!

remi

Directory Structure

SKILL.md

Report

Notice