Repository navigation
Classify sessions by intent, optionally by Claude from all prompts - #10
Merged
Merged
Conversation
Every session gets an intent - bug fix, new development, refactoring, tests, planning & design, docs & content, ops & config, review, research & analysis or other - from rules over its commit messages and PR titles, review commands, title, git branch prefix, first prompt and the files it changed. The adoption report adds a Session intent section and a summary line; JSON carries each session's intent and the evidence for it. Claude Code, Copilot and Cursor loaders record the branch, first prompt, commit messages and changed files. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A new `intents` report lists each session's intent and evidence; in JSON it also carries the signals (title, first prompt, branches, commit messages, changed files per kind, the rules' guess). `--intents <file>` applies intents assigned elsewhere to any report, replacing the rules' guess with evidence "claude". The skill exports the signals, classifies the sessions itself and reruns the report with --intents. Bare slash commands (/clear) no longer count as the first prompt, and "create a tool / app / page" counts as new development. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The intents signals now carry every prompt typed in a session, in order (resumed copies once, bare slash commands and interrupts left out, each cut at 500 characters), instead of only the first. The skill reads them all and judges the session as a whole. The rules keep using the first prompt. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
# Conflicts: # src/adoption.mjs # src/cursor.mjs # src/loader.mjs
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Classifies every session by intent: bug fix, new development, refactoring, tests, planning & design, docs & content, ops & config, review, research & analysis, or other.
Rules (default, offline). The strongest signal wins:
fix:,feat:,refactor:…)/code-review,/review,/security-review)fix/,feature/…), then the first promptThe adoption report gets a Session intent section (sessions, share, PRs, edits, tokens and cost per intent) and a summary line. JSON gives each session's
intentandintentEvidence.Classified by Claude (skill).
ccreports intentsreport: each session's intent and evidence. With-jit also includes the signals: title, every prompt typed in the session, branches, commit messages, changed files by kind, and the rules' guess.--intents <file>option: applies intents assigned elsewhere ({"<session id>": "<intent>"}) to any report, replacing the rules' guess, with evidenceclaude.--intents.The loaders record the git branch (Claude Code and Copilot; Cursor logs none), the prompts, commit messages and PR titles, and the changed files.
Prompt text is never shown in a report. It only appears in
intents -j, the signals export the skill reads.Overlap with #9
This branch is based on
mainand doesn't include the working habits metrics (#9). Both branches add file tracking to the loaders (editFiles/writeFile,patchFiles). Whichever merges second will have small conflicts to resolve:patchFilesreturns{ updated, added }here, but a plain list in #9.Test plan
npm test: 60 tests pass, including newtest/intent.test.mjs, loader signal tests, and tests forparseIntents, the--intentsoverride and the intents reportspecs/read as tests, a bare/cleartaken as the first prompt, "create a tool" not counted as new development)adoption --intents🤖 Generated with Claude Code