fix: standardize frontmatter and composer.json paths#12
Conversation
Signed-off-by: Sebastian Mendel <info@sebastianmendel.de>
Summary of ChangesHello @CybotTM, 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 addresses a configuration discrepancy by correcting the path for the Highlights
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.
Pull request overview
Updates the Composer package metadata so the netresearch/composer-agent-skill-plugin can locate this skill’s SKILL.md in its actual location under skills/cli-tools/.
Changes:
- Fix
composer.jsonextra.ai-agent-skillpath toskills/cli-tools/SKILL.md.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Summary
extra.ai-agent-skillpath to point to actual SKILL.md locationContext
The
extra.ai-agent-skillpath was pointing toSKILL.mdat repo root, but the actual file is atskills/cli-tools/SKILL.md.