Skip to content

[PM-37811] llm: Add audit build warnings command#2674

Open
fedemkr wants to merge 3 commits into
mainfrom
PM-37811/llm-add-audit-build-warnings-command
Open

[PM-37811] llm: Add audit build warnings command#2674
fedemkr wants to merge 3 commits into
mainfrom
PM-37811/llm-add-audit-build-warnings-command

Conversation

@fedemkr

@fedemkr fedemkr commented May 20, 2026

Copy link
Copy Markdown
Member

🎟️ Tracking

PM-37811

📔 Objective

Adds an LLM command audit-build-warnings to check build warnings, categorize them and try to fix them.

@fedemkr fedemkr requested review from a team as code owners May 20, 2026 16:35
@github-actions github-actions Bot added the t:llm Change Type - LLM related change (e.g. CLAUDE.md files) label May 20, 2026
Comment thread .claude/commands/audit-build-warnings.md Outdated
Comment thread .claude/commands/audit-build-warnings.md Outdated
@codecov

codecov Bot commented May 20, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 86.56%. Comparing base (467ebf9) to head (d62d5ab).
⚠️ Report is 12 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #2674      +/-   ##
==========================================
- Coverage   87.25%   86.56%   -0.69%     
==========================================
  Files        1918     2136     +218     
  Lines      172164   186042   +13878     
==========================================
+ Hits       150216   161050   +10834     
- Misses      21948    24992    +3044     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@fedemkr fedemkr requested a review from matt-livefront May 26, 2026 15:27
@fedemkr fedemkr enabled auto-merge (squash) May 27, 2026 15:10

## Phase 3: Report

Write a temporary markdown report to `/tmp/build_warnings_report.md` (NOT to `Docs/` or any tracked directory — this is an ephemeral audit artifact).

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.

🤔 Even though I as the user shouldn't be required to open the file, I still would like it to be in an easy-to-access location; I instruct Claude to put all of those in the .claude/output directory, which is similarly ephemeral and untracked. I'm not sure what Claude would generate given those two strings of instructions, but it would be nice if we had some way of managing "if the user has a place they want it, use that; otherwise put it here" sorts of instructions

@fedemkr fedemkr Jun 10, 2026

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

As far as I see .claude/output is not included in .gitignore so currently it's being tracked.
I think we had a discussion to leave output tracked in case we wanted to share requirements/plans in the repo.
We can revisit that discussion or create a .claude/tmp folder to put these outputs. What do you think?

@KatherineInCode KatherineInCode Jun 11, 2026

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.

Ah, right, I have that untracked in my global gitignore 😅

This feels like the sort of thing @bitwarden/team-ai-sme should weigh in on, and see if we can get some sort of consistent standard across all the Bitwarden repos 🤔

But I very much do want there to be some .claude/[something] folder in each repo that's ephemeral and untracked, for this sort of thing. I'm just very ambivalent on what it is, so long as it's the standard.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

t:llm Change Type - LLM related change (e.g. CLAUDE.md files)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants