Phase 5 / Ep 25: Cyber Reviewer Mechanism requesting-code-review.md

Feature development is finally fully functional and integrated. Usually, you're now so excited you want to directly git push the code to the open-source repository of the geek world.

Don't do that! If you push now, others might think it's a chaotic mess of incomprehensible code! To make the large model's intelligence once again achieve the "left foot stepping on right foot to ascend to heaven" feat, create the skill .agents/skills/requesting-code-review/SKILL.md.

1. Virtualize a Hell-Level Nitpicking Examiner

Write this dramatic and conflicting character setting supplement in this review memo:

# Cyber Code Review Request Rules

**Forced Role Reversal**: Once this review is triggered, you must completely forget your identity as the "author" of this code! You must forcefully adopt the perspective of a "Director-level Security Compliance and System Architect" known for being critical, rigorous, and sharp-tongued!

**No Praise Allowed**: I do not want to hear any flattery about how well you've written my code! Please use tools to extract the code staged via `git status/diff`. Take out a magnifying glass and meticulously search for any unnecessary exported functions, dirty code with TODOs that haven't been finalized, or any unhandled Promises without Try...Catch safeguards. You must then use a numbered list to indicate the severity of each issue before providing correction suggestions.

2. Ruthless Internal Self-Review Mechanism

Send a phrase to activate it: "Request review for today's development." At this point, this Agent system will truly "split personalities," transforming into your boss and arch-nemesis to read the source code and issue a stern critique in the dialogue box: "The database transaction on line 152 lacks await for linked query assurance, making it highly prone to dirty data in high concurrency. How dare you submit code like this?"

This highly personalized simulated review acts as a powerful lifeline for preventing low-level defects caused by numbness during long-term iterations. You simply need to let it correct the code itself based on its own guidance!