engineering

Pack path: engineering/

Skills

• GitHub Triage — Use when triaging GitHub issues or incoming bug reports. Covers fast issue review, category and state decisions, codebase context gathering, next-action recommendations, and preparing issues for implementation without jumping straight into code.
• Improve Codebase Architecture — Use when exploring a codebase for architectural improvement opportunities. Covers finding shallow modules, identifying bad seams, proposing deeper boundaries, and turning structural friction into concrete refactor candidates.
• Request Refactor Plan — Use when planning a refactor before implementation starts. Covers scope clarification, alternatives, testing strategy, tiny-commit sequencing, and writing a refactor plan that stays durable even if the code layout changes.
• Setup Conventional Commits — Use when configuring a repo to enforce Conventional Commits locally without making commit flow annoying. Covers commitlint, Husky commit-msg hooks, minimal config choices, and the rule that semantic commits should improve history quality, not add ceremony.
• Setup Pre-Commit — Use when setting up pre-commit automation in a JavaScript or TypeScript repo. Covers Husky, lint-staged, formatter setup, package-manager-aware hook commands, and keeping commit-time checks realistic.
• TDD — Use when building a feature or fixing a bug with test-driven development. Covers red-green-refactor, vertical slices, public-interface tests, and sequencing implementation around one behavior at a time.
• Triage Issue — Use when investigating a bug before fixing it. Covers fast diagnosis, root-cause tracing, narrowing repro paths, checking adjacent code and tests, and producing a concrete fix plan instead of guessing.
• Write Decision Complete Feature Spec — Use when a feature needs a real implementation spec before coding starts. Covers goal and success criteria, user-facing behavior, boundaries, non-goals, edge cases, acceptance checks, and the rule that the spec should remove implementation guesswork instead of just sounding thorough.
• Write Intentional Commit Message — Use when writing or reviewing a commit message and the real challenge is choosing the correct Conventional Commit type, scope, and summary based on change intent. Covers commit splitting, amend vs new commit decisions, and avoiding vague or misleading commit titles.