How do I install the Engineering Quality skill?

Run npx skillmds@latest add ashermahonin/engineering-quality in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Engineering Quality safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Engineering Quality?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Engineering Quality free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Engineering Quality?

ashermahonin (@ashermahonin) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Engineering Quality by ashermahonin

Name: Engineering Quality
Author: ashermahonin

Engineering Quality

Review the maintainability of production code and guide focused refactoring through clear names, cohesive modules, explicit dependencies, controlled side effects, actionable errors, readable tests, and small change sets. Use during implementation planning, code review, legacy cleanup, or a refactor where behavior must remain stable. Do not activate for formatting-only edits or as permission to rewrite unrelated code.

ashermahonin Updated Sep 21, 2026

File contents

Engineering quality

Purpose

Keep code understandable under change. This skill supplies the maintainability contract; the implementation skill owns production edits and the test skill owns behavioral proof.

Change context

Read the request, affected code, tests, and local conventions.
Identify the behavior that must remain stable and the specific maintenance problem being solved.
Separate observed problems from stylistic preference.
Read references/engineering-quality.md for the decision criteria.

Change method

Map the changed responsibilities, dependencies, side effects, and public contracts.
Find the smallest structural issue that affects correctness, readability, testability, or future change cost.
Prefer a local correction: clearer name, smaller responsibility, explicit dependency, simpler control flow, stronger boundary, or removal of proven duplication.
Reject abstractions that only prepare for hypothetical reuse.
Preserve behavior with the affected test suite. When behavior changes, require an acceptance criterion and regression test.
Check errors, logs, and comments from the caller's point of view.
Report any wider debt separately instead of expanding the patch.

Evidence

The maintenance problem and its concrete impact
The narrowest useful change or review finding
Behavior-preservation evidence
Any compatibility, migration, or rollback concern
Deferred debt that remains outside scope

Ready when

Names and structure express the domain without explanatory noise.
Responsibilities and dependencies are visible at the right boundary.
Side effects and failure behavior are explicit.
Tests describe behavior rather than mirror the implementation.
The patch contains no unrelated cleanup.
Performance claims are measured, not assumed.

Handoff

Pass the scoped recommendation to service-implementation, or report findings through pr-review. Include the exact tests that protect the behavior.

References

references/engineering-quality.md: maintainability and clean-code decision contract.

---name: engineering-qualitydescription: Review the maintainability of production code and guide focused refactoring through clear names, cohesive modules, explicit dependencies, controlled side effects, actionable errors, readable tests, and small change sets. Use during implementation planning, code review, legacy cleanup, or a refactor where behavior must remain stable. Do not activate for formatting-only edits or as permission to rewrite unrelated code.---# Engineering quality## PurposeKeep code understandable under change. This skill supplies the maintainability contract; the implementation skill owns production edits and the test skill owns behavioral proof.## Change context- Read the request, affected code, tests, and local conventions.- Identify the behavior that must remain stable and the specific maintenance problem being solved.- Separate observed problems from stylistic preference.- Read `references/engineering-quality.md` for the decision criteria.## Change method1. Map the changed responsibilities, dependencies, side effects, and public contracts.2. Find the smallest structural issue that affects correctness, readability, testability, or future change cost.3. Prefer a local correction: clearer name, smaller responsibility, explicit dependency, simpler control flow, stronger boundary, or removal of proven duplication.4. Reject abstractions that only prepare for hypothetical reuse.5. Preserve behavior with the affected test suite. When behavior changes, require an acceptance criterion and regression test.6. Check errors, logs, and comments from the caller's point of view.7. Report any wider debt separately instead of expanding the patch.## Evidence- The maintenance problem and its concrete impact- The narrowest useful change or review finding- Behavior-preservation evidence- Any compatibility, migration, or rollback concern- Deferred debt that remains outside scope## Ready when- Names and structure express the domain without explanatory noise.- Responsibilities and dependencies are visible at the right boundary.- Side effects and failure behavior are explicit.- Tests describe behavior rather than mirror the implementation.- The patch contains no unrelated cleanup.- Performance claims are measured, not assumed.## HandoffPass the scoped recommendation to `service-implementation`, or report findings through `pr-review`. Include the exact tests that protect the behavior.## References- `references/engineering-quality.md`: maintainability and clean-code decision contract.

Frequently asked questions