Skip to content

docs: clarify guideline priority ordering in CLAUDE.md - #36296

Merged
mateo-berri merged 1 commit into
litellm_internal_stagingfrom
litellm_claude_md_descending_importance
Aug 8, 2026
Merged

docs: clarify guideline priority ordering in CLAUDE.md#36296
mateo-berri merged 1 commit into
litellm_internal_stagingfrom
litellm_claude_md_descending_importance

Conversation

@devin-ai-integration

Copy link
Copy Markdown
Contributor

TLDR

Problem this solves:

  • "In that order of importance" reads ambiguously

How it solves it:

  • Say "In descending order of importance" instead

User Flow

Not applicable, this only edits contributor guideline wording in CLAUDE.md

Relevant issues

Linear ticket

Pre-Submission checklist

  • I have added meaningful tests
  • My PR passes all CI/CD checks (e.g., lint, format, unit tests)
  • My PR's scope is as isolated as possible; it only solves 1 specific problem
  • I have received a Greptile Confidence Score of at least 4/5 before requesting a maintainer review

Note: no tests apply, this is a one line documentation wording change

Screenshots / Proof of Fix

No runtime behavior changes, so there is nothing to exercise against a live proxy

Type

📖 Documentation

Changes

Reworded the line under the code quality priority list in CLAUDE.md from "In that order of importance" to "In descending order of importance", making it explicit that "correct" ranks highest and "modern" lowest

Link to Devin session: https://app.devin.ai/sessions/3cec3a6ccc4c4ab2aac6517864f05ad3
Requested by: @mateo-berri

Co-Authored-By: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
@mateo-berri mateo-berri self-assigned this Aug 8, 2026
@devin-ai-integration

Copy link
Copy Markdown
Contributor Author

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

  • Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
  • Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

  • Disable automatic comment, CI, and merge conflict monitoring

@mateo-berri mateo-berri left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@mateo-berri
mateo-berri enabled auto-merge August 8, 2026 19:56
@greptile-apps

greptile-apps Bot commented Aug 8, 2026

Copy link
Copy Markdown
Contributor

Greptile Summary

Clarifies the priority ordering of code-quality guidelines without changing their meaning or runtime behavior.

  • Replaces “In that order of importance” with the more explicit “In descending order of importance.”
  • Makes clear that correctness is the highest priority and modernity the lowest.

Confidence Score: 5/5

The documentation-only clarification appears safe to merge.

The revised sentence accurately and unambiguously describes the existing list’s intended highest-to-lowest priority ordering, with no conflicting guidance or runtime impact.

Important Files Changed

Filename Overview
CLAUDE.md The one-line wording clarification is consistent with the surrounding ordered guidance and introduces no actionable issue.

Reviews (1): Last reviewed commit: "docs: clarify guideline priority orderin..." | Re-trigger Greptile

@mateo-berri
mateo-berri merged commit 554f065 into litellm_internal_staging Aug 8, 2026
75 checks passed
@mateo-berri
mateo-berri deleted the litellm_claude_md_descending_importance branch August 8, 2026 20:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant