Conversation
Summary of ChangesHello @noamteyssier, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request enhances developer experience by integrating specific guidance for Claude AI, enabling it to better understand and interact with the codebase. Concurrently, it simplifies the project's configuration setup by removing redundant or outdated tool configurations, contributing to a cleaner and more maintainable project structure. Highlights
🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console. Changelog
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
There was a problem hiding this comment.
Code Review
This pull request introduces a CLAUDE.md file to provide context for an AI assistant and removes some configuration files. My review focuses on improving the clarity of the new documentation and pointing out a potentially unintended side effect of removing the ruff.toml configuration file, which could impact the project's code style and linting enforcement.
I am having trouble creating individual review comments. Click here to see my feedback.
ruff.toml (1-5)
Removing ruff.toml will cause ruff to fall back to its default settings. This is a significant change, as it will, for example, reduce the max-line-length from 120 to 88 and change the set of active linting rules (the ERA rule for commented-out code will be disabled).
If this is unintentional, you should move the configuration to pyproject.toml. Here is how you can do it:
[tool.ruff]
line-length = 120
[tool.ruff.lint]
select = ["E", "F", "ERA"]This will preserve the project's current code style and linting rules.
CLAUDE.md (68-69)
For better clarity and to ensure the AI assistant can find the exact metrics, it would be beneficial to use the precise metric names as registered in src/cell_eval/metrics/_impl.py, and use wildcards for metric families. This will make the documentation more accurate.
For example:
discrimination_scoreis registered asdiscrimination_score_{distance_metric}(e.g.,discrimination_score_l1).edistanceis registered aspearson_edistance.overlap/precision at Ncorresponds tooverlap_at_*andprecision_at_*.spearman correlationscorresponds tode_spearman_*metrics.
- **AnnData metrics** (`_anndata.py`): `pearson_delta`, `mse`, `mae`, `mse_delta`, `mae_delta`, `discrimination_score_*`, `clustering_agreement`, `pearson_edistance`
- **DE metrics** (`_de.py`): `overlap_at_*`, `precision_at_*`, `de_spearman_*`, `de_direction_match`, `de_sig_genes_recall`, `pr_auc`, `roc_auc`
No description provided.