GitHub Copilot app for Beginners: How to teach Copilot about your codebase
Learn how to add custom instructions and skills to your repository, use custom agents, and connect MCP servers like Playwright. The post GitHub Copilot app for Beginners: How to teach Copilot about your codebase appeared first on The GitHub Blog.
Learn how to add custom instructions and skills to your repository, use custom agents, and connect MCP servers like Playwright. The post GitHub Copilot app for Beginners: How to teach Copilot about your codebase appeared first on The GitHub Blog.
In context
- Topic: Desarrollo con IA — Copilotos y agentes en el ciclo de desarrollo de software.
- Source: The GitHub Blog
- Published: 12/10/2026
Continue reading at the original source →
Excerpt published automatically by the site radar. The full text belongs to its publisher and is linked above.
Why it matters
When a tool appears promising faster development, the useful question is not how much code it generates but how much work it generates downstream. Tests, review, security, technical debt, incidents: that is where the promise gets paid or charged.
I look at it from operations, not from the demo. The question is not whether the assistant writes a correct function, but whether the team can maintain what it produced six months later, with different people, without the original context. That is the real test and it almost never appears in the announcements.
What usually goes wrong
The problem appears when somebody accepts code they do not fully understand but which passes the tests. It works, it ships, and six months later it needs changing. That is when you discover nobody on the team can explain why it is written that way, and the small change becomes a rewrite.
What to watch
- Whether total time to production drops or only writing time, which is not the same thing.
- What happens to code review: if the assistant produces more, somebody has to read more.
- What happens to tests — generating code without generating tests only moves the problem forward.
How I read this entry
I would treat it as a process change, not a tool change. The assistant shifts who does what inside the team, and that has to be discussed with people beforehand, not discovered in the retrospective once somebody already felt replaced.
This entry is an excerpt from the original source, selected by the site radar. The commentary above is the site's own and does not belong to the cited publisher.
Comments
No comments yet. Yours can be the first.
Living through this in your own team?
Open the chat and tell me how you're handling it. I'm interested in comparing notes.
