Post

I just released my first agent skill: /do-i-understand As a technical educator for many years, I want to maintain my own skill and that of those around me. This agent skill makes sure you understand what you're shipping before you merge it. Here's how it works 👇

Run /do-i-understand and it looks at the change you're about to push (or point it at earlier commits). It prioritizes changes, then probes your reasoning, your assumptions, and the ways the change could fail. It's looking for the parts you don't yet fully understand.

At the end it writes a short report. Paste it into your PR description for your reviewer, or keep it as a personal record. The goal is simple: *push code only once you can be accountable for it*.

Second, with junior engineers. Require it on their PRs, but build the safe space first. "I don't know" has to be a welcome answer, one that invites pair coding and mentorship instead of something to hide.

Third, for open source maintainers. You can ask for a do-i-understand report in PRs as a light honor-system check. It's a bit of intentional friction before a merge request. Free and open, link below. I really enjoy using it, so let me know what you think.

0 reposts0 likes