codeeagle-meetings

Files (1)

• SKILL.md

SKILL.md (first lines)

# CodeEagle — Meeting Transcripts

Meetings hold the part of a project's reasoning that never reaches the
codebase: why a design was chosen, what was ruled out, and who owns what next.
Use this skill when the question is about what people *said*, not what the code
does.

## Answering "what was said about X, by whom, and when"

Start with `search`. One call returns, per meeting, the date, the participants,
and the exact place the words matched — a topic label, a segment with its
summary, a decision with its quote, a follow-up with its owner:

```bash
codeeagle meetings search AGI                          # newest first among equal matches
codeeagle meetings search "Okta CIAM" --full           # untruncated summaries and quotes
codeeagle meetings search pricing --person Kevin       # only meetings someone attended
codeeagle meetings search --only decision --since 2026-08-01   # every decision since a date
codeeagle meetings search --only follow-up --person Mona --json
```

Words match whole and case-insensitively ("AGI" does not match "messaging"),
a word of four or more letters also matches the start of a longer one, and an
initialism counts as one with its expansion. When `transcripts.jev_api_key` is
configured, the matched meetings are ordered by a decision model's probability
that each one answers the question (printed as `p=0.82` beside the meeting;
the header says what it cost); `--no-rerank` keeps word-match order. No
generative model is ever called. `codeeagle rag "<words>"` searches by meaning
instead, across code and documents as well as meetings.

A search also reaches past the words themselves. Each meeting names its subject
in its own words, so "AGI" alone would miss one filed under "AGI feasibility
debate"; related topics are linked by probability and a search follows those
links, discounting each hop so a direct match always outranks a neighbour.

```bash
codeeagle meetings search AGI --breadth wide     # follow further, more recall
codeeagle meetings search AGI --breadth none     # only what matched the words
```

`none`, `narrow`, `default` and `wide`. This depends on the links existing --
see *Linking topics* below. Without them every breadth behaves like `none`.

## Listing and reading meetings

```bash
codeeagle meetings list --limit 20            # most recent first, with a short id
codeeagle meetings list --person "Kevin"      # meetings someone attended
codeeagle meetings list --since 2026-03-01    # meetings after a date
codeeagle meetings list --who                 # show attendee names, not a count
codeeagle meetings list --json                # machine-readable
```

Then read one in full — participants with speaking time, topics with their own
summaries and timestamps, decisions with supporting quotes, and follow-ups:

```bash
codeeagle meetings show <meeting-id>
codeeagle meetings show a99b3645               # a prefix of the id is enough
codeeagle meetings show "auth" --json          # partial title match also works
```

A reference that several meetings answer to is refused with the candidates
listed; nothing is picked silently. Listings that are cut short say so and say
how to see the rest — read a listing that does not say so as complete.

## People and commitments

```bash
codeeagle meetings people                      # who appears, how often, what they own
codeeagle meetings actions --person "Kevin"    # what someone committed to
codeeagle meetings actions --unassigned        # follow-ups nobody owns
codeeagle meetings topics                      # what gets discussed most (capped; says so)
codeeagle meetings topics agi                  # only the topics containing a word
```

## Indexing

```bash
codeeagle meetings sync --dry-run              # scope and token cost, no model call
codeeagle meetings sync                        # enrich and index; skips unchanged
codeeagle meetings watch                       # index new recordings as they appear
```

`watch` runs in the foreground and sweeps on an interval rather than waiting on
filesystem events, because a recording is written over the course of a meeting
and an event arrives while the file is still growing. Nothing installs it as a
service, so recordings made while it is not running wait for the next `sync` or
the next `watch` — whose first sweep catches up.

### Linking topics

One-off, and only useful with `transcripts.jev_api_key` set. Judging which
topics are about the same thing is what makes `--breadth` find anything:

```bash
codeeagle meetings relate --dry-run            # count the pairs, judge none
codeeagle meetings relate                      # judge them
```

New meetings are linked as they are indexed, so this is a catch-up for a corpus
indexed before the links existed. `codeeagle meetings taxonomy` groups the flat
topic labels into concepts, and `--rebuild` regroups them from scratch.

### Moving a corpus

```bash
codeeagle meetings migrate --from <branch>     # move an older corpus into scope
codeeagle meetings migrate --from-db <path>    # ...or out of another database
```

## Reading the output honestly

Two things in this data need care:

- **Speakers may be unidentified.** Recordings are diarized but anonymous, and
  a name is only asserted when the transcript supports it — leaving a speaker
  unnamed is a deliberate outcome, not a bug. `codeeagle meetings identify`
  lists what is unresolved, and `codeeagle meetings label "Person 3" Kevin

From imyousuf/CodeEagle, Apache-2.0.

More from imyousuf/CodeEagle