unknowns-merge-quiz
Skill2 starsChanged 4 months agoMITView on GitHub
Verify understanding of a diff or completed change before merge. Use when the user asks to be quizzed before merging, wants to ensure they understand what changed, needs a merge-readiness report, or wants an artifact that tests comprehension and points wrong answers back to the relevant explanation.
In this repository11 other files it gives its agents.
- know-your-unknownsSkill
- unknowns-blindspot-passSkill
- unknowns-buy-in-docSkill
- unknowns-design-directionsSkill
- unknowns-domain-bootstrapSkill
- unknowns-implementation-notesSkill
- unknowns-intervention-brainstormSkill
- unknowns-mock-before-wireSkill
- unknowns-reference-mapSkill
- unknowns-spec-interviewSkill
- unknowns-tweakable-planSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 20
Stop condition: the user can answer the quiz correctly or has reread the missed sections.
- Distinctive: line 26
Use HTML when scoring, answer reveal, and remediation links make the gate more effective.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Unknowns Merge Quiz
Workflow
Convert "I skimmed the diff" into tested understanding.
Return:
- Mental model of the change.
- What changed and why.
- Non-obvious behavior introduced.
- Risks, dependencies, and rollback notes.
- 5-8 questions that test understanding, not trivia.
- For each question: answer, explanation, and remediation pointer.
- Stop condition: the user can answer the quiz correctly or has reread the missed sections.
Rules
Ground the quiz in the actual diff, tests, and behavior. Ask about implications and invariants, not line-number trivia.
Use HTML when scoring, answer reveal, and remediation links make the gate more effective.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.