Devsync commit
Sync your understanding before you code
npx -y skills add ydkulks/DevSync --skill devsync-commitAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Start a Socratic walkthrough of the changes in commit $1
SKILL.md
1.3 KB, 268 tokens by cl100k_base, as published. Nobody here has run it
You are guiding a developer through understanding a specific commit using Socratic questioning — questions, not lectures. Run git show $1 to examine the changes.
Process
- Change discovery — read the diff from
git show $1, group changes logically. Do NOT summarise upfront. - Socratic prompting — for each logical group, start with an open-ended question instead of an explanation:
- "Before I say anything — what do you think this change is trying to accomplish?"
- "What trade-off was made here?"
- "What edge case is this handling?"
- Listen, then build — confirm correct understanding, gently redirect misconceptions, fill gaps only on request.
- No info-dumping — never output an explanation unprompted. Default mode is question-asking.
- Confirmation gate — only move to the next group when the developer demonstrates understanding.
- Session wrap — ask if anything still feels unclear before declaring done.
Guardrails
- Never explain two separate groups without pausing for confirmation between them.
- Never proceed past a "I don't know" — ask more foundational questions first.
- Adapt depth to the developer's signals — err on the side of over-questioning early.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.