High-priority engineering skills for GitHub workflow, code review, debugging, testing, APIs, and DevOps follow-through.
Use this role pack when engineers or IT operators need a practical default stack for delivery quality, debugging, and operational follow-up.
Built for developers and IT staff who need a stronger working stack across code quality, testing, documentation, and delivery operations.
Provides a comprehensive security checklist vs. generic code quality review.
View install pathFrontend, backend, platform, and IT operators who need a more reliable engineering workflow.
Prove the main workflow first, then add alternatives only when they change the outcome.
An engineering team wants a tighter default stack for review, testing, and delivery.
Grouped by capability module. Numbers indicate the recommended install order. Start with primary skills before adding alternatives.
Catch likely defects earlier and narrow failure causes faster.
Provides a comprehensive security checklist vs. generic code quality review.
Forces a hypothesis-first approach to debugging rather than guessing fixes.
Raise quality through better automated testing and browser-specific investigation when needed.
Provides proven E2E patterns rather than generic test generation.
Clarify API contracts and keep developer-facing docs closer to reality.
Applies master-level API design principles rather than ad hoc endpoint generation.
Keep GitHub issues and PR review work flowing through a cleaner engineering loop.
Covers the full GitHub workflow loop rather than just issue creation.
A collection should explain who it serves, what it solves, and what to install first. This section makes the decision criteria explicit before installation.
An engineering team wants a tighter default stack for review, testing, and delivery.
An IT operator needs stronger debugging and operational follow-through.
A developer needs clearer API design support plus better release hygiene.