Eng Change Checklist
Short checklist of engineering principles to apply before and after non-trivial work. Use when planning or reviewing a non-trivial change, debugging a stubborn failure, designing types or boundaries, or deciding how to sequence a migration.
Install
npx skills add jpoehnelt/skills --skill eng-change-checklistgit clone --depth 1 https://github.com/jpoehnelt/skills.git /tmp/skills
mkdir -p ~/.claude/skills
cp -r /tmp/skills/eng-change-checklist ~/.claude/skills/eng-change-checklistPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Engineering change checklist Apply the ones that fit. Each is a habit, not a ceremony. Repo-specific rules (test policy, compatibility-layer format, validation library) live in the repo's AGENTS.md or CLAUDE.md and win over this list. ## Principles - **Fix root causes.** Trace the symptom back to the first wrong decision and fix it there. A guard, retry, or clamp is a fix only when the state it handles is legitimate. Reproduce first, instrument instead of guessing, and fix every instance of the same fault. - **Prove it works.** Check the real artifact: run the feature, read the actual value, inspect the diff. Do not accept "it compiles", a cached view, or an agent's self-report. Prefer a script a reviewer can re-run. If a check fails, suspect the observation method first. - **Subtract before you add.** Remove dead code, redundant validators, and stubs first, then build on the simpler base. Design for observed usage, not speculative edge cases. Leave the design simpler than you found it. - **"Unused" means unused by the whole stack.** In a stacked PR series or a slice with no caller yet, a search of one branch cannot prove a parameter or export is dead. Before deleting one, `git grep` it on every open branch stacked on this one and read the linked issue's scope. If a sibling calls it or the issue requires it, keep it. If you still cut it, say in the PR body that it moved to a later slice.
Details
- Skill name
eng-change-checklist- Repository
- jpoehnelt/skills
- Path
eng-change-checklist/SKILL.md- License
- MIT
- Repo updated
- 12 November 2026
FAQ
What does the Eng Change Checklist skill do?
Short checklist of engineering principles to apply before and after non-trivial work. Use when planning or reviewing a non-trivial change, debugging a stubborn failure, designing types or boundaries, or deciding how to sequence a migration.
How do I install the Eng Change Checklist skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add jpoehnelt/skills --skill eng-change-checklist. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Eng Change Checklist popular?
It lives in jpoehnelt/skills, which has 23 GitHub stars and 1 forks.
Related skills
Agents Correct
23jpoehnelt/skills
Find the mistakes agents keep repeating in a repo and make each one impossible, trying architecture first, then types, lint, tests, and docs last. Use when the operator keeps correcting the same mistake, or for /agents-correct.
Agents Create Verification Skill
23jpoehnelt/skills
Generate a project-local verify skill that drives the app like a user through a browser with Playwright, a CLI, or HTTP. Use for /agents-create-verification-skill, "make a verify skill for this repo", or when a project has no scripted way to prove UI, CLI, or service behavior.
Agents Reflect
23jpoehnelt/skills
After a work session, review what went wrong and right and turn each lesson into a concrete edit to an existing skill or AGENTS.md line. Use when the user says "reflect" or /agents-reflect.
Formatting Notion Pages
9mattppal/formatting-notion-pages
Apply rich formatting to Notion pages - toggles, callouts, headers, and styled text. Use when creating or formatting Notion documents via the Notion MCP server.
Comms Impact
23jpoehnelt/skills
State what a change means for users and the business in plain words, as "When <who> does <what>, <now>. Before, <then>." Use when writing the impact part of a PR description, change note, changeset, release note, incident summary, or status update, or when someone asks what a change does for users.
Memanto
9moorcheh-ai/memanto-agent-skills
Store and retrieve persistent agent memory with the MEMANTO CLI. Use whenever the user states a decision, preference, correction, or commitment worth keeping; whenever you are about to say you lack context on prior work; or when asked what was decided, preferred, or promised earlier. Covers remember, recall, answer, edit/forget, file upload, conflict resolution, expiry policy, and MEMORY.md sync.
Browse the most popular Claude skills, all productivity & notes skills, or write your own with the skills generator.