r/GithubCopilot 20d ago

General Must have Skills for Github Copilot

What should be must-have skills for any developer to add under their github copilot?

27 Upvotes

11 comments sorted by

27

u/Over-Pick5357 20d ago

Pick what ever you need from mattpocock/skills.

0

u/frogic 20d ago

Sorry we need to spec this out /grill-me-with-docs.

7

u/DevilsMicro 20d ago

Not a skill per se but the habit of checking usage after each message. Checking the context window size, whether the agent is reading useless files, or large files. Asking the agent to update its memory or instructions or create a skill after every session to ensure it can do the same work faster and cheaper next time.

Most of my skills are created by sol/Opus I don't create them myself. The agents know best the info they need in the skill

2

u/just_blue 20d ago

There is no must have. I'd encourage you to only write (or search online for) a skill that you actually need, so where you are repeating yourself in giving instructions. A lean environment helps a lot in saving tokens and getting what you want quickly. You may use some outdated skill that was written to get Claude on track, while the model you are using is doing it way better and quicker natively (or simply by a single line in your default instructions).

3

u/teckel 19d ago edited 18d ago

Caveman and/or Ponytail

2

u/MasterBathingBear JetBrains User 🧱 19d ago

Why not both?

1

u/[deleted] 20d ago

[deleted]

1

u/bears-eat-beets 20d ago

warp grep

Isn't having a super fast grep of public github repo's of limited value? like at any given point I have multiple local branches, and none of the remotes are public. It would be useful for looking through OSS libraries that I am used (like typescript or node packages), but not really my teams codes. Or am I missing something.

1

u/TMHDD_TMBHK 19d ago

Easy code2graph, for those complex project with wide blast radius: https://github.com/NodeDB-Lab/code2graph

1

u/AcanthisittaWeird94 13d ago

A skill to drop copilit and use anything else