No prior experience required. Imposter syndrome welcome.
5 Unfair Advantages You Deserve to Know About
faster code completion
reported by developers
of new code written
by Copilot suggestions
Translation: you'll ship twice as fast as the team in the corner who refused to use AI on principle.
You don't even have to open your IDE to start winning.
That little β¨ sparkle button appears all over GitHub.com. Here's where to find it:
Ask Copilot to summarize a giant PR, explain a confusing issue, or suggest a fix β right in the thread.
Use natural language to search your repo. "Find where we handle auth errors" actually works now.
Ask "what does this repo do?" on any public repo. Instant onboarding. Your teammates will be jealous.
Copilot auto-generates PR descriptions. Your "fixed stuff" commit messages finally get a proper writeup.
Request a Copilot code review on any PR. It'll find bugs you definitely put there on purpose to test it.
Get help fixing broken CI pipelines without having to understand YAML. A true gift.
The Copilot Chat panel is your co-pilot (get it?) throughout the GitHub UI.
@@github to search across all of GitHub, docs, and your orgGitHub's agentic features let Copilot do entire tasks, not just suggest code.
VS Code, JetBrains, Vim... yes, even Vim. We don't judge.
Inline suggestions are Copilot's bread and butter. Here's how to use them like a pro:
# Calculate distance between two GPS coordinates
# using the Haversine formula
def haversine(lat1, lon1, lat2, lon2):
# β¨ Copilot writes the whole thing...
R = 6371 # Earth radius in km
dlat = radians(lat2 - lat1)
dlon = radians(lon2 - lon1)
a = sin(dlat/2)**2 + cos(radians(lat1)) \
* cos(radians(lat2)) * sin(dlon/2)**2
return R * 2 * asin(sqrt(a))
You wrote the comment. Copilot wrote everything else. You're basically a software architect now.
A full conversational AI assistant embedded right where you're coding β with context-aware variables, slash commands, and specialized agents.
#file β attach a specific file#selection β your highlighted code#codebase β entire project#editor β active editor content#git β git history & diffs#terminalLastCommand β last output + any errors
/new react app with typescript β scaffold instantly β¨/newNotebook titanic dataset β Jupyter notebook/fix β make it not broken/tests using Jest β write tests/explain β what does this do?/doc β document this
@workspace β whole codebase (VS Code)@project β whole codebase (JetBrains)@vscode β IDE settings & keybindings@terminal β shell & command line help@github β search across GitHub
/new node.js express server with JWT auth in chat β preview the file tree β create all files β you have a working scaffold in 30 seconds.
#terminalLastCommand explain this error and fix it β apply the diff β green. No copy-paste required.
Copilot Edits lets you make multi-file changes with a single prompt. This is the "I need to refactor everything" button.
Copilot doesn't play favorites. Much.
The flagship experience. Fullest feature set. If you're not using this, are you even a developer?
Completions Chat Edits Agent /new @workspaceIntelliJ, PyCharm, GoLand, WebStorm. Full chat experience β use @project instead of @workspace.
Classic Windows development. Use #file and #solution for context. No judgment for using it.
For the 0.1% who will absolutely mention it during the hackathon presentation.
Completions ChatiOS and macOS devs, you're included! Swift completions work great.
CompletionsStill alive. Still supported. Attach files with the paperclip icon in the Chat panel.
Completions Chat /fix /testsTerminal warriors, your moment has arrived.
Not just a command suggester β a terminal-native AI coding partner that can work autonomously, delegate tasks, plan implementations, and manage sessions. Invoke it with copilot.
Generates a structured implementation plan with checkboxes before writing a single line of code. Asks clarifying questions, saves to plan.md, and waits for your approval.
Offloads work to the Copilot cloud agent β creates a PR asynchronously while you keep working locally.
/help to see all available commands. The CLI is continually evolving and /help always shows the most up-to-date capabilities.
The golden workflow for complex hackathon features β models achieve higher success rates when given a concrete plan to follow.
# 1. EXPLORE β understand first, don't code yet
Read the auth files but don't write code yet
# 2. PLAN β create a structured plan
/plan Add OAuth2 with Google and GitHub providers
# Copilot asks clarifying questions,
# creates a checklist plan, saves to plan.md,
# and waits for YOUR approval before proceeding
# 3. IMPLEMENT β execute the approved plan
Proceed with the plan
# 4. VERIFY β don't skip this step
Run the tests and fix any failures
# 5. COMMIT β clean history
Commit these changes with a descriptive message
Never worry about context limits. The CLI automatically compacts conversation history while preserving essential information.
/session # View session info
/session plan # See current plan
/context # Visualize token usage
/compact # Manually compact (rarely needed)
/clear # Start fresh (better for unrelated tasks)
# Add other repos to the session
/add-dir /path/to/other-service
/list-dirs # See what's in scope
copilot from a parent directory containing all your repos β it can see and edit across all of them simultaneously.
/fleet breaks a task into parallel subtasks run by sub-agents simultaneously/delegate sends work to the cloud agent so you can keep coding locally/fleet Migrate all class components to functional components β sub-agents tackle each file in parallel.
# Allow git commands without asking each time
copilot --allow-tool='shell(git:*)'
# Deny a specific dangerous command
copilot --deny-tool='shell(git push)'
# Reset all previously approved tools
/reset-allowed-tools
Mission control for your AI agents. macOS, Windows, and Linux.
A downloadable desktop app (not just a website) that is the only agent-native development experience built natively on GitHub. Currently in Technical Preview
The app keeps humans in control while agents do the heavy lifting.
The only plan you need for hackathon glory.
copilot CLI with /plan when something's complex. Use Copilot Edits to make sweeping changes fast.
The quality of Copilot's output is proportional to the quality of your prompt. Here's the formula:
Set up custom instructions so Copilot always knows your project's context before you ask anything.
Create a .github/copilot-instructions.md file:
# Project: HackathonApp
## Stack
- React + TypeScript frontend
- FastAPI Python backend
- PostgreSQL database
- Deployed on Railway
## Conventions
- Use async/await, never callbacks
- All API responses use { data, error }
- Prefer functional components
- Write tests for all API endpoints
## Context
This is a hackathon project for
tracking team productivity metrics.
Set in GitHub Copilot settings for your personal style:
Stop explaining context. Start encoding it.
Custom agents are specialized versions of the Copilot agent β defined once, reused forever. They encode your conventions, frameworks, and desired outcomes directly into Copilot.
A Markdown file with YAML frontmatter at .github/agents/NAME.md:
---
name: api-builder
description: Builds REST API endpoints
following our conventions
---
You are an API specialist for this
project. Always:
- Use FastAPI with async handlers
- Return { data, error } objects
- Add input validation with Pydantic
- Write tests for every endpoint
- Follow our OpenAPI spec in /docs
.github/agents/ β repo-level (team shared).github repo β org-wide.github-private β everyoneapi-builder.md, test-writer.md, and readme-creator.md. Assign issues to specific agents by name. Each knows exactly what to do.
Skills are folders of instructions, scripts, and resources that Copilot loads automatically when relevant. Based on an open standard.
Committed to the repo β shared with your whole hackathon team:
.github/skills/
.agents/skills/
In your home directory β travel with you across every project:
~/.copilot/skills/
github/awesome-copilotanthropics/skillsgh skill install <repo>gh skill install for your stack (React, FastAPI, etc.). Copilot now knows your framework's conventions without a single prompt.
Remember: Copilot writes code. You write good code. The difference is you still review everything.
A tool is only as good as the person wielding it. You've got this.