engineering-fundamentals

Review code naming, structure, and refactoring against DRY and SOLID principles.

274|18|Updated Dec 23, 2025
One-click install
npx skills add https://github.com/DanielPodolsky/ownyourcode --skill engineering-fundamentals
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: engineering-fundamentals
Source: https://github.com/DanielPodolsky/ownyourcode/tree/main/.claude/skills/fundamentals/engineering
Command: npx skills add https://github.com/DanielPodolsky/ownyourcode --skill engineering-fundamentals

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps software teams elevate code quality by providing a structured framework for evaluating naming, structure, and refactoring decisions.

Core Features & Use Cases

  • Naming discipline: ensures descriptive, non-abbreviated identifiers and consistent boolean prefixes.
  • Code organization: encourages DRY, cohesion, and clear separation of concerns.
  • Guided reviews: a repeatable checklist approach used during code reviews and junior mentoring.
  • Use Case: a mid-project refactor where you audit modules for single responsibility and testability.

Quick Start

Use this skill during a code review to assess naming, function size, and module design, then apply improvements to a sample function under review.

Frequently Asked Questions about engineering-fundamentals

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review code quality during a pull request using DRY and SOLID principles?

Improve code quality during a pull request by applying a structured checklist that evaluates naming, function size, and single responsibility. This enforces DRY and SOLID principles while ensuring separation of concerns and readability across the modified modules.

What is the best way to refactor existing modules for single responsibility and testability?

Refactor existing modules for testability by auditing them methodically against established best practices. Evaluate code organization and cohesion to ensure clear separation of concerns and strict adherence to DRY principles.

How does naming discipline impact code readability and maintainability?

Naming discipline improves code readability and maintainability by enforcing descriptive, non-abbreviated identifiers and consistent boolean prefixes. This structured approach ensures variables and functions clearly express intent across the project.

Can I use a code review checklist to mentor junior developers on code organization?

Yes, you can use a repeatable checklist approach to mentor junior developers on code organization. It provides a structured framework for evaluating naming, structure, and refactoring decisions during guided reviews.

When do I need to apply code refactoring guidelines during a mid-project audit?

Apply code refactoring guidelines during a mid-project audit when evaluating modules for single responsibility and testability. This ensures the codebase maintains readability, maintainability, and adherence to best practices as it evolves.