skills.rest
tankpkg
tankpkgOFFICIAL
Explore all skills by this author →
GitHub

@tank/professional-programmer

Review code and change plans for production readiness and explicit tradeoffs.

1|1|Updated Feb 20, 2026
Search Tags:#testing#code review#debugging#refactoring#tradeoffs#software craftsmanship#professional programming
One-click install
npx skills add https://github.com/tankpkg/packages --skill tank-professional-programmer
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: @tank/professional-programmer
Source: https://github.com/tankpkg/packages/tree/main/skills/professional-programmer
Command: npx skills add https://github.com/tankpkg/packages --skill tank-professional-programmer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

It helps you make professional engineering decisions when code needs to be correct, maintainable, testable, safe to change, and ready to ship. Use it when you need stronger judgment than a basic code generator can provide.

Core Features & Use Cases

  • Production-quality implementation: Choose the smallest correct design, surface tradeoffs clearly, and avoid speculative abstraction.
  • Testing and verification discipline: Favor behavior-focused tests, characterization tests, and regression guards that survive refactors.
  • Refactoring and debugging safety: Make changes in narrow steps, protect behavior, and add durable fixes instead of temporary guesses.
  • Delivery and collaboration hygiene: Improve code review quality, estimate with assumptions, document decisions, and support reliable releases.
  • Use case: Review a messy feature before merge, decide whether to abstract or simplify, harden a risky bug fix, or assess whether a change is actually ship-ready.

Quick Start

Ask this skill to review your code, change plan, or bug fix for production readiness, explicit tradeoffs, test coverage, safe refactoring, and professional delivery standards.

Frequently Asked Questions about @tank/professional-programmer

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

FAQPage Schema
How do I ensure my code is production-ready before shipping a new feature?▼

To review code before merge, assess production readiness by checking for explicit tradeoff reasoning, behavior-focused test coverage, safe refactoring steps, and professional delivery standards. This ensures the change is safe to ship.

What is the best way to write tests that survive future refactoring?▼

To debug and harden a risky bug fix, make changes in narrow steps to protect behavior and add durable fixes instead of temporary guesses. Apply explicit tradeoff reasoning to ensure the solution is maintainable.

How do I decide whether to abstract a design or simplify it during development?▼

Refactoring requires making changes in narrow steps to protect existing behavior while adding durable fixes instead of temporary guesses. Prioritize behavior-focused verification and regression guards to maintain production safety.

When should I not use speculative abstraction in software engineering?▼

To ensure production readiness, verify explicit tradeoff reasoning, behavior-focused test coverage, safe refactoring practices, and professional delivery standards. Assess whether the change is correct, maintainable, and safe to ship.

Related Skills

Explore More Software Engineering Skills→
intelligentcode-aiintelligentcode-ai
35

thinking

Decompose complex decisions into explicit step-by-step analysis and validation plans.

Official
Advanced
qa-amanqa-aman
19

qa-execution

Plan, execute, and document QA test cycles with structured inputs and summaries.

Community
Intermediate
knckknckknckknck

go-style-guide

Standardize Go code quality and style across projects.

Community
Intermediate
j-cogburnj-cogburn

source-driven-development

Verify framework-specific code against official version-specific documentation.

Community
Advanced