Skip to content

chore: add Serena project memories#137

Open
JohnRDOrazio wants to merge 4 commits intodevfrom
chore/add-serena-memories
Open

chore: add Serena project memories#137
JohnRDOrazio wants to merge 4 commits intodevfrom
chore/add-serena-memories

Conversation

@JohnRDOrazio
Copy link
Copy Markdown
Member

Summary

  • Commit Serena MCP memory files generated by onboarding
  • Add .worktrees/ to .gitignore (project-local git worktrees convention)

Why

Serena's .serena/memories/*.md files capture project-specific knowledge — overview, structure, suggested commands, code style, and a task-completion checklist — that Serena writes during onboarding. Committing these means:

  • Fresh checkouts and new worktrees activate the project with full context immediately
  • Teammates using Serena MCP share the same baseline knowledge
  • No per-machine, per-branch re-onboarding overhead

Files

  • .serena/memories/project_overview.md
  • .serena/memories/project_structure.md
  • .serena/memories/suggested_commands.md
  • .serena/memories/code_style_and_conventions.md
  • .serena/memories/task_completion_checklist.md

Serena's inner .serena/.gitignore (already present in the .serena directory and not part of this PR) excludes cache/ and project.local.yml automatically, so transient state never gets committed.

Test plan

  • CI is green
  • git status shows clean tree after merge (no untracked .serena/ paths showing as needing commit)

🤖 Generated with Claude Code

Persist Serena MCP project memory files (.serena/memories/) so they
travel with the repo. Future sessions, fresh checkouts, and worktrees
activate the project with full onboarding context (overview, structure,
suggested commands, code style, task completion checklist) without
re-running onboarding.

Also add .worktrees/ to .gitignore for project-local git worktree usage.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented Apr 28, 2026

Warning

Rate limit exceeded

@JohnRDOrazio has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 20 minutes and 18 seconds before requesting another review.

To keep reviews running without waiting, you can enable usage-based add-on for your organization. This allows additional reviews beyond the hourly cap. Account admins can enable it under billing.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 281ea6cd-f594-49d5-98a5-8bb7d5f548bf

📥 Commits

Reviewing files that changed from the base of the PR and between 978883d and 58b1499.

📒 Files selected for processing (8)
  • .gitignore
  • .serena/.gitignore
  • .serena/memories/code_style_and_conventions.md
  • .serena/memories/project_overview.md
  • .serena/memories/project_structure.md
  • .serena/memories/suggested_commands.md
  • .serena/memories/task_completion_checklist.md
  • .serena/project.yml
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch chore/add-serena-memories

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@codecov
Copy link
Copy Markdown

codecov Bot commented Apr 28, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ All tests successful. No failed tests found.

📢 Thoughts on this report? Let us know!

JohnRDOrazio and others added 3 commits April 28, 2026 08:45
….yml)

Follow-up to the memories commit. Persist Serena's auto-generated project
config so fresh checkouts and worktrees activate Serena cleanly without
regenerating these files:

- .serena/.gitignore: ignores transient state (cache/, project.local.yml)
- .serena/project.yml: project name, language, encoding for Serena's LSP
  bootstrapping

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Set per-project initial_prompt that Serena always injects on activation
(unlike memories, which load on demand). Captures the small set of
project-specific rules where forgetting causes real damage —
branch/PR targets, anti-patterns, key invariants. Kept tight on purpose
to bound the per-session token cost.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
- Replace machine-specific absolute path in `## Repo Location` (was
  `/home/johnrdorazio/development/...`)
- Label unlabeled fenced code blocks as `text` so MD040 passes and
  rendering is unambiguous

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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