Skip to content

docs: lean CLAUDE.md (claude-md-lint)#26

Merged
saagpatel merged 2 commits into
mainfrom
docs/claude-md-lint
May 31, 2026
Merged

docs: lean CLAUDE.md (claude-md-lint)#26
saagpatel merged 2 commits into
mainfrom
docs/claude-md-lint

Conversation

@saagpatel
Copy link
Copy Markdown
Owner

Leaned the project CLAUDE.md via claude-md-lint, rebuilt against current main (298→95 lines). Whole-file no-loss gate: all 10 protected tokens preserved (commands, port 9876, ~/job-search-2026/). Corrected the auto-block's wrong 'npm only' claim — repo uses pnpm (pnpm-lock.yaml + CI). Auto-generated portfolio-context block left intact. Hand-leaned because its auto-block is mid-file (sandwiched), a case the batch tool doesn't handle.

@saagpatel saagpatel merged commit aa2315e into main May 31, 2026
3 checks passed
@saagpatel saagpatel deleted the docs/claude-md-lint branch May 31, 2026 08:02
Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 7508c8b4e8

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread CLAUDE.md
## Gotchas

## Development Conventions
- **Package manager is pnpm, not npm.** `pnpm-lock.yaml` is authoritative and CI runs `pnpm install --frozen-lockfile`; `package-lock.json` is an orphan from the template. The auto-generated portfolio-context block below still claims "npm only" — that claim is wrong; trust this section. (The block regenerates from memory each auditor run, so the contradiction may reappear until the generator reads CI as ground truth.)
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P2 Badge Keep npm lockfile authoritative for release builds

In contexts where a dependency changes, this new guidance tells agents to trust pnpm-lock.yaml and treat package-lock.json as an orphan, but the checked release workflow (.github/workflows/release.yml) still runs npm ci, which is a clean install driven by npm's lockfile. Following this instruction would let future changes update only the pnpm lock, leaving release builds to fail or ship a different dependency graph; it also conflicts with the repo-root AGENTS.md npm-only rule.

Useful? React with 👍 / 👎.

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