core-engineering

Review code diffs and generate implementations with production-grade engineering standards.

15|2|Updated Dec 13, 2025
One-click install
npx skills add https://github.com/d-padmanabhan/agent-engineering-handbook --skill core-engineering-d-padmanabhan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: core-engineering
Source: https://github.com/d-padmanabhan/agent-engineering-handbook/tree/main/skills/core-engineering
Command: npx skills add https://github.com/d-padmanabhan/agent-engineering-handbook --skill core-engineering-d-padmanabhan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Core Engineering Standards help you avoid unsafe, hard-to-maintain, or non-production-ready code by providing consistent principles for review and generation.

Core Features & Use Cases

  • Review with a priority framework: triages issues by criticality (security/data loss vs maintainability vs optional improvements) to focus agent feedback.
  • Generation guardrails for completeness and safety: drives agents to ask up to three high-impact questions when ambiguous, and to output complete runnable code without placeholders.
  • Tooling and dependency baselines: standardizes linting/formatting and security scanning expectations (plus repo-wide scanning for secrets and CVEs).
  • Production checks for cross-cutting risks: enforces strong error-handling, observability, testing intent, Unicode/time/number correctness, and dependency vetting.

Quick Start

Use the core-engineering skill to review the agent’s proposed changes by asking it to list the Critical, Recommended, and Optional issues relative to production readiness and security-first standards.

Frequently Asked Questions about core-engineering

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

FAQPage Schema
How do I structure code review feedback by severity for production readiness?

Code review feedback is structured by severity to prioritize production readiness, separating critical security and data loss issues from recommended maintainability improvements and optional enhancements. This triage framework focuses agent feedback on high-impact risks first.

What is the best way to generate runnable code that includes error handling and observability?

Generating runnable code with error handling and observability requires production-grade engineering principles and security-first guardrails. This approach drives agents to ask up to three high-impact questions when ambiguous and outputs complete implementations without placeholders.

How do I vet dependencies and standardize secure coding practices across different tech stacks?

Vetting dependencies and standardizing secure coding practices across stacks requires establishing tooling baselines for linting, formatting, and security scanning. This includes enforcing repo-wide scanning for secrets and CVEs alongside dependency vetting checks.

How do I prevent AI code generation from fabricating APIs and making unverified security claims?

Preventing AI code generation from fabricating APIs and making unverified security claims requires applying security-first guardrails and production checks. This enforces strong error-handling, testing intent, and correctness for Unicode, time, and number handling.

What cross-cutting risks should I check when evaluating code diffs for production deployment?

Evaluating code diffs for production deployment requires checking cross-cutting risks including strong error-handling, observability, testing intent, Unicode, time, and number correctness, and dependency vetting. This ensures the code is secure and production-ready.