Repository navigation
feat: your skill and knowledge review requests in Claude Code — /altimate-code:rules, decision toasts, publish relays the review #22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
601e70d
5ea6247
aa2e348
cc48cd0
d29d068
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -123,7 +123,9 @@ In a project linked to an Altimate workspace, the workspace's approved **team ru | |
| - **At session start** the plugin gives Claude the team rules for this repository, tells it how many proposed rules are waiting for you, and reports the owner's reviews of your proposals since your last session (approved, or rejected with the reason). | ||
| - **When you correct Claude** ("no, we never use FLOAT for money") the correction is recorded locally. When you correct it on the same topic in two sessions, or correct a team rule it was given, altimate-code words a proposed rule after the turn, in the background. | ||
| - **"Remember this as a team rule: …"**, said to Claude, waits as a proposal the same way. It needs "as a rule" or "team rule" followed by ":" or "-": "remember to run the tests", a question, or "don't remember this as a team rule" is just part of the conversation. A task handed to altimate-code decides this as an altimate-code session does. | ||
| - **`/altimate-code:rules`** shows the proposals waiting for you, the team rules, and the status of the rules you proposed. For each proposal you choose: send it to the workspace owner's review (or approve it, if you are the owner), edit the wording, save it as a memory, or "Not a rule". Nothing reaches teammates until the owner approves it. | ||
| - **`/altimate-code:rules`** shows the proposals waiting for you, the team rules, and the status of the rules you proposed. For each proposal you choose: send it to the workspace owner's review (or approve it, if you are the owner), edit the wording, save it as a memory, or "Not a rule". Nothing reaches teammates until the owner approves it. It also lists your skill and knowledge requests to the workspace (waiting, approved, rejected with the reason, or removed), read-only: withdrawing a request or removing an approved skill or knowledge base happens in the Altimate web app, altimate-code's TUI (`/rules`) or its VS Code extension. | ||
| - **Decisions on your skill and knowledge requests** are told to Claude at session start, and shown to you as a toast once each: at session start and every 15 minutes while an interactive session runs. This needs an altimate-code release with `workspace review decisions`; with an older one there are no toasts. | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. [SUGGESTION]: "shown to you as a toast once each" describes more than the code does
|
||
| - **`skill publish`** from a session says whether the skill was sent for the owner's review or is already in the workspace. | ||
|
|
||
| Rule drafting uses altimate-code's own model (sign in to the Altimate LLM Gateway, or set a provider in altimate-code): if it has none it can use, the next session start says the check failed. The same commands work in a terminal: `altimate learn proposals`, `altimate learn proposals reply <id> --send`. Proposals from Claude Code sessions are answered only there or with `/altimate-code:rules`: altimate-code's own `/rules` and its VS Code chat panel don't list them. This needs an altimate-code release with workspace rules. | ||
|
|
||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[SUGGESTION]: "Last revised" now precedes the document's own latest change entry
The same policy's "Changes to this policy" log (line 154, added with the 1.6.0 lineage-report release) is dated November 16, 2026, so setting "Last revised" to November 13, 2026 here makes the revision date older than a change the document already records, and the new 1.7.0 section added by this PR still has no dated entry in that log. Use the release date (2026-11-17, as in
CHANGELOG.md) and add a dated line for "Your skill and knowledge requests" (plugin 1.7.0).