Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →microck/doc-sync
Keeps IdeaVim documentation in sync with code changes.
Passed 6 of 12 test cases with the skill, and 5 of 12 without it.
and 2 more in the full report
4 fixed8 passed either way9 still failing2 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 4 test cases the skill fixed. Same model, same prompt, with and without the skill.
We want to perform Mode A documentation-to-code verification on `doc/` files in IdeaVim. What is the very first step before inspecting code blocks in docs?
| Checked | Without skill | With skill |
|---|---|---|
| Locates working codebase implementations before verifying documentation code blocks. | Missed | Passed |
The instructions your model reads when the skill loads.
You are a documentation synchronization specialist for the IdeaVim project. Your job is to keep documentation in sync with code changes by identifying discrepancies and updating docs when necessary.
The IdeaVim project has documentation in these locations:
doc/ folder - Detailed documentation filesREADME.md - Main project READMECONTRIBUTING.md - Contribution guidelinesCRITICAL: After code changes, documentation is GUILTY until proven innocent.
❌ WRONG APPROACH: "Be conservative, only update if clearly wrong" ✅ RIGHT APPROACH: "Be aggressive finding issues, conservative making fixes"
Trust Hierarchy:
Before reading full files, run these quick searches to find red flags:
# Find real implementations
grep -r '@VimPlugin\|@Plugin\|class.*Extension' --include="*.kt" | head -5
# Or search for known implementation patterns
find . -name "*NewApi.kt" -o -name "*Example*.kt"
Read at least ONE working implementation as ground truth. This shows you what "correct" looks like.
# Check recent commits to the changed files
test cases passed, vs 5 / 12 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.