First off - thank you! 💜 Every contribution makes the arena better for everyone.
You don't need to write code to help. Open an Issue for any of these:
- 🐛 Report a bug - Did the hackathon break mid-run? Tell us!
- 💡 Suggest a feature - New scoring criteria? Tournament modes? Let us know!
- ✏️ Fix a typo - Spotted a mistake? We appreciate it!
- 🎨 UX feedback - Was the ceremony dramatic enough? 🏟️
- Fork this repo
- Create a branch:
git checkout -b my-improvement - Make your changes - see the development guide below
- Test your changes - see TESTING.md
- Open a PR - fill out the template and describe what you changed
- GitHub Copilot CLI installed
- An active Copilot subscription
-
Clone the repo:
git clone https://github.com/DUBSOpenHub/havoc-hackathon.git cd havoc-hackathon -
Register the skill locally in a Copilot CLI session:
/skills add ./ -
Test a hackathon run:
run hackathon - write a fizzbuzz function -
Verify your changes against the TESTING.md playbooks.
- 🎭 Keep the MC energy - this is a hackathon, not a board meeting!
- ⚖️ Fair play - judging logic must stay unbiased
- 🔒 Sealed judging - never leak model identity to judges
- 📋 Evidence-based - scoring must cite evidence
- 🧪 Test your changes - run through the conversation flow
- 🔄 Keep SKILL.md in sync - the skill file exists in two locations (
skills/havoc-hackathon/SKILL.mdand.github/skills/havoc-hackathon/SKILL.md). If you edit one, copy the changes to the other so they stay identical.
- Keep PRs focused - one improvement per PR
- Update CHANGELOG.md with your change
- Follow existing file naming conventions
- If changing scoring logic, explain the rationale
Please read our Code of Conduct. We're building an inclusive community! 💜