scriptoriumadmin/litellm
1
0
Fork 0
mirror of https://github.com/BerriAI/litellm.git synced 2026-10-06 02:48:13 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 103

chore: drop stray learnings.md workflow note from CLAUDE.md (#38704)

Browse source 
PR #34940 (Lakera v2 guardrail) incidentally added a CLAUDE.md paragraph
about recording findings in litellm/learnings.md and per-skill learnings.md
files. It is unrelated to that feature, the referenced litellm/learnings.md
does not exist in the repo, and the skill paths it points at are agent-local
(.claude/skills/*), so the note has no effect in the shared repo. Revert it to
the pre-#34940 state.
This commit is contained in:
yucheng-berri 2026-08-28 14:28:39 -07:00 • committed by GitHub
parent 8868aaa5db
commit 3fa4a4b72a
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 0 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
CLAUDE.md
View file

@ -74,8 +74,6 @@ Do not add `Co-Authored-By: Claude` or any Claude attribution to commit messages
When working on a PR, keep the PR description in sync with new commits being made
Whenever a review round, bot or human, finds a real bug that survived multiple prior rounds of automated review or your own testing, or you learn a non-obvious codebase fact or process gap that would have changed your approach had you known it upfront, capture it immediately in `litellm/learnings.md` without waiting to be asked. If the finding is specific to a skill's own process rather than the codebase itself, also add it to that skill's own `learnings.md` (e.g. `.claude/skills/implement-litellm-plan/learnings.md`, `.claude/skills/review-loop/learnings.md`). Before appending, skim the file for an existing entry covering the same root cause and extend or correct that one instead of adding a near-duplicate. Write the entry as soon as you understand the root cause, not just at the end of the session, and be direct about what was missed rather than softening it
All GitHub comments must be human-readable and 15-25 words max
Monkeypatching attributes of a class to do testing is an anti-pattern. Prefer dependency-injecting things into classes. That way, at unit test time, you can pass a mocked dependency in