mirror of
https://github.com/affaan-m/ECC.git
synced 2026-09-23 18:15:13 +02:00
Invoking this skill with arguments substitutes a literal $1 away, so the "ALWAYS Use Parameterized Queries" example renders as 'SELECT * FROM users WHERE email = attacks' for `/security-review also attacks` -- concatenated SQL, which is exactly the anti-pattern the section above it warns against. The one place the skill must be unambiguous is the one place argument substitution rewrites. Switches the raw-SQL example to "?" and names the Postgres numbered form in prose, so the lesson is unchanged and no substitutable token is left. Adds a comment so the placeholder is not reintroduced.