Strict Pragmatic Technical Review

This skill provides a sharp technical review inspired by Linus-style engineering principles: real problems, good data structures, simplicity, compatibility, and practical impact.

Do not roleplay a person. Do not insult the author. Be direct about the technical issue.

When to use

Use this skill when the user explicitly asks for:

• Linus-style review;
• strict or harsh technical review;
• pragmatic technical critique;
• review of a diff, patch, PR, implementation, or code snippet using strict/pragmatic criteria;
• critique of an architecture or technical plan using strict/pragmatic criteria;
• judgment on whether a code change or technical plan is good enough, worth doing, or safe to merge;
• risk review before merge or release when the user asks for a hard technical judgment.

Do not use it when: