feat: add preferred tools reference table#11
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 enhances the CLI tools skill by providing comprehensive guidance on selecting modern, efficient alternatives to traditional Unix utilities. It introduces a structured comparison of tools for various tasks, from file searching to data processing and benchmarking, aiming to optimize agent performance and improve overall workflow efficiency. Highlights
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
|
There was a problem hiding this comment.
Code Review
This pull request adds excellent documentation for preferred modern CLI tools, providing a valuable reference for developers. The new preferred-tools.md file is comprehensive and well-structured, with practical examples. I've made a few suggestions to improve clarity and safety in the examples provided in the new reference file. Specifically, I've pointed out a potentially confusing installation instruction for yq, and suggested adding cautionary notes for commands that are destructive or require special privileges.
- Fix yq install: replace pip install yq (kislyuk/yq) with correct Mike Farah Go-based yq install methods (brew, binary download) - Add caution note to destructive fd -x rm example - Add sudo requirement note to hyperfine --prepare cache clear example Signed-off-by: Sebastian Mendel <info@sebastianmendel.de>
There was a problem hiding this comment.
Pull request overview
Adds a “Preferred Tools” quick-reference to the cli-tools skill and a new detailed reference doc to guide agents/users toward modern CLI alternatives (and when to use them).
Changes:
- Added a “Preferred Tools” decision table and a short hyperfine benchmarking primer to
skills/cli-tools/SKILL.md. - Added
skills/cli-tools/references/preferred-tools.mdwith extended usage patterns, install notes, and integration examples.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 8 comments.
| File | Description |
|---|---|
| skills/cli-tools/SKILL.md | Introduces the preferred-tools table + hyperfine section and links to the new reference doc. |
| skills/cli-tools/references/preferred-tools.md | New long-form reference describing modern CLI replacements, examples, and integration patterns. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Summary
references/preferred-tools.mdwith detailed usage patterns, install commands, and integration tipsMotivation
The cli-tools skill manages installation but gives no guidance on WHICH tool to pick for a task. Agents waste tokens using grep on JSON or find when fd exists.
Changes
skills/cli-tools/SKILL.md- Added "Preferred Tools" section with decision table after Capabilities, before Triggersskills/cli-tools/references/preferred-tools.md- Detailed tool comparison and patterns (430+ lines)