feat: add react-doctor skill to react category#8
Conversation
Summary of ChangesHello @runkids, 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 integrates the "react-doctor" skill into the system, expanding the available tools within the React category. This addition provides users with a new capability to analyze and assess the quality, security, and performance of their React projects. 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
Activity
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
|
Skill Audit ResultsAudited 1 sources across 1 repos.
Audit Details
|
There was a problem hiding this comment.
Code Review
This pull request adds the react-doctor skill to the react category. The implementation is straightforward and follows the project's contribution guidelines. I have one suggestion to improve the data by removing a redundant skill property, which I've detailed in a comment.
| "source": "millionco/react-doctor", | ||
| "skill": "react-doctor", |
There was a problem hiding this comment.
The skill property appears to be redundant here, as its value is the same as name. The project's schema defines skill as an optional field for use in multi-skill repositories. Since this seems to be a single-skill repository, omitting this property would make the entry cleaner and more aligned with the schema's intent. The suggested change removes the skill property and the now-unnecessary trailing comma from the source property.
"source": "millionco/react-doctor"
What
add react-doctor skill
Skill Entry
[ { "name": "react-doctor", "description": "Scans your React codebase for security, performance, correctness, and architecture issues. Outputs a 0-100 score with actionable diagnostics.", "source": "millionco/react-doctor", "skill": "react-doctor", "tags": [ "react", "frontend" ] } ]Checklist
skills/*.jsoncategory file (see CONTRIBUTING.md)nameis lowercase with hyphens onlydescriptionis a clear one-linersourcerepo is publicly accessible and contains a validSKILL.md