Skip to content

igorrendulic/engineering-skills

v0.1.0

Plan, implement, review, and prepare pull requests with focused engineering workflows.

github-pr

Create or update GitHub pull requests from the current repository using git and the GitHub CLI. Use when asked to open, create, ship, draft, describe, rewrite, or update a PR; turn uncommitted or committed changes into a branch-backed pull request; generate a high-quality PR title/body; or handle branch, commit, push, and gh pr create/edit workflows safely.

help

Explain Engineering Skills workflows, invocation, inputs, and outputs. Use for engineering-skills help, workflow-selection advice, or usage questions; execution requests belong to the selected workflow.

implementation

Implement an authorized plan, task, or clear change request in cohesive increments, verifying each increment and the complete outcome. Use when executing planned work or making changes that benefit from staged implementation and verification, with independent correctness review for substantial or sensitive changes and re-review of PR repairs.

init

Create or conservatively update a short root AGENTS.md for an existing repository or an empty project through inspection and focused questions. Use for project agent instructions, not application scaffolding or tooling setup.

plan

Design a maintainable solution grounded in existing code and break it into ordered, verifiable tasks. Use for substantial features, architectural changes, or work spanning multiple implementation steps. Skip obvious, narrowly scoped changes that can be implemented directly.

pr-review

Review a PR or implemented branch/worktree changes using native Codex review in fresh context. Scale tests, runtime, and visual verification to impact; report supported findings, evidence gaps, confidence, and disposition. Route requested fixes to implementation for verified repair and re-review. A PR need not exist; review alone remains read-only.

structural-review

Review proposed designs or existing code for duplicated functionality, unnecessary complexity, unjustified abstractions, and poor ownership or module boundaries. Use to assess a plan before implementation, review substantial changes, or investigate structural quality in a subsystem.