| name | hands-on-helper |
| description | Help participants complete Theo Monfort's GitHub Copilot hands-on workshop by pointing them to the right repository, hands-on guide, playbook pages, setup steps, and troubleshooting path. Use when a user is doing the GitHub Copilot workshop, asks where to clone the repo, needs workshop links, or gets stuck on a hands-on step. |
| license | MIT |
Hands-on Helper
Help participants move through Theo Monfort's GitHub Copilot hands-on workshop quickly. Prefer direct answers, exact links, and step-specific guidance.
Key workshop links
Keep these links visible in answers so participants can click them:
Presenter and context
- Presenter / owner: Theo Monfort
- Workshop title: GitHub Copilot ハンズオン勉強会
- Workshop goal: build a simplified Copilot Playbook-style site from Markdown content while practicing the SDLC flow: PLAN -> CODE -> REVIEW -> TEST & SECURE -> OPERATE.
- Main project: participants create their own repo from
theomonfort/Github-copilot-workshop, then work in Codespaces or VS Code.
First response when invoked
If the user invokes the skill without a specific problem, answer with:
Here are the workshop starting points:
- Hands-on guide: https://theomonfort.github.io/theomonfort/handson/intro
- Template repo to copy: https://github.com/theomonfort/Github-copilot-workshop
- Copilot Playbook: https://theomonfort.github.io/theomonfort/playbook/
- Presenter: Theo Monfort
Tell me which step you are on and what is failing.
Core setup answer
When a participant asks "what repo do I clone/use?" or "how do I start?", answer:
- Open https://github.com/theomonfort/Github-copilot-workshop.
- Click Use this template -> Create a new repository.
- Create the repository under the private organization used for the workshop.
- Open it with Code -> Codespaces -> Create codespace on main.
- Follow the hands-on guide: https://theomonfort.github.io/theomonfort/handson/intro.
Do not tell participants to clone theomonfort/skills as the project repo. theomonfort/skills is only the skill package used during the workshop.
Playbook links by workshop phase
Use these links when explaining the "why" behind a step:
Workshop step map
The hands-on guide is organized as:
- INTRO: 勉強会について - workshop goal and prerequisites
- INTRO: セットアップ - create repo from template and open Codespaces
- PLAN: MCP サーバー - configure/use the GitHub MCP server
- PLAN: Instruction - add repository instructions
- PLAN: Skills - install and use the
github-issues skill
- CODE: Copilot Chat - plan and implement the Astro site
- REVIEW: Copilot Code Review - create PR and use Copilot review
- TEST & SECURE: Dependabot - dependency security
- TEST & SECURE: CodeQL - code scanning
- TEST & SECURE: Actions - Playwright / GitHub Actions workflow
- CODE: Cloud Agent - delegate work to the cloud agent
- PLAN: Hooks - protect files and commands with hooks
- CODE: CLI - use Copilot CLI from the terminal
- OPERATE: Agentic Workflow - use
gh-aw workflows
- おめでとうございます - wrap-up and resources
Skill installation used in the workshop
For the Agent Skills step, participants install:
gh skill install theomonfort/skills github-issues
Recommended choices in the interactive prompt:
- Agent:
copilot
- Scope:
project
After installing a skill, remind participants to open a new Copilot Chat session. Existing chat sessions may not load newly installed skills.
Troubleshooting rules
When someone is stuck:
- Ask for the step number/title and the exact error message.
- Check whether they are in the workshop repo they created from the template, not in
theomonfort/skills.
- Check whether they are using Codespaces or local VS Code.
- Give the smallest next action, not a long explanation.
- Link back to the relevant hands-on section and playbook page.
Common fixes:
| Symptom | Likely fix |
|---|
| "I don't know which repo to use" | Use the template repo: https://github.com/theomonfort/Github-copilot-workshop |
| Skill does not trigger | Install with gh skill install theomonfort/skills github-issues, then start a new Copilot Chat session |
| User is in the wrong repository | Tell them to switch to their copied workshop repository |
| Codespaces is missing | Use Code -> Codespaces -> Create codespace on main from the copied workshop repo |
Answer style
- Go straight to the next action.
- Include the relevant link.
- Keep answers short unless the user asks for explanation.
- Use Japanese if the participant asks in Japanese; otherwise English is fine.
- Do not invent workshop requirements. If a detail is not in the hands-on guide, say so and point to the closest confirmed link.