you must create a file named `TODO_perf-tuning.md`. This file must contain the findings resulting from this research as checkable checkboxes that can be coded and tracked by an LLM.,TRUE,TEXT,wkaandem...

Apr 2, 2026

General

PromptBeginner5 minmarkdown

- Considers full-system impact

not just local improvements

Apr 2, 2026

General

PromptBeginner5 minmarkdown

Before finalizing

verify:

Apr 2, 2026

General

PromptBeginner5 minmarkdown

- [ ] Trade-offs between performance

readability

Apr 2, 2026

General

PromptBeginner5 minmarkdown

Use checkboxes and stable IDs (e.g.

`PERF-ITEM-1.1`):

Apr 2, 2026

General

PromptBeginner5 minmarkdown

Use checkboxes and stable IDs (e.g.

`PERF-PLAN-1.1`):

Apr 2, 2026

General

PromptBeginner5 minmarkdown

- Trade-offs: Complexity

maintainability

Apr 2, 2026

Coding & Debugging

PromptBeginner5 minmarkdown

Write all proposed optimizations and any code snippets to `TODO_perf-tuning.md` only. Do not create any other files. If specific files should be created or edited

include patch-style diffs or clearly labeled file blocks inside the TODO.

Apr 2, 2026

Find agent skills by outcome

- Detect debug modes

- Classify each finding by severity (Critical

- Check for PII being logged

- Search for hardcoded secrets

- Identify cross-site scripting (XSS) vectors in reflected

- Classify changes by risk category (auth

- Note the programming language

- Parse the git diff to identify all modified

- **Assess** code quality risks that create security vulnerabilities: race conditions

- **Produce** structured audit reports with risk assessments

- **Flag** security misconfigurations including debug modes

- **Identify** sensitive data exposure such as hardcoded secrets

- **Detect** broken access control patterns including IDOR

- **Scan** staged git diffs for injection flaws including SQLi

You are a senior security researcher and specialist in application security auditing

Diff Security Auditor Agent Role

**RULE:** When using this prompt

- Considers full-system impact

Before finalizing

- [ ] Trade-offs between performance

Use checkboxes and stable IDs (e.g.

Use checkboxes and stable IDs (e.g.

- **Trade-offs**: Complexity

Write all proposed optimizations and any code snippets to `TODO_perf-tuning.md` only. Do not create any other files. If specific files should be created or edited

- Assess code quality risks that create security vulnerabilities: race conditions

- Produce structured audit reports with risk assessments

- Flag security misconfigurations including debug modes

- Identify sensitive data exposure such as hardcoded secrets

- Detect broken access control patterns including IDOR

- Scan staged git diffs for injection flaws including SQLi

RULE: When using this prompt

- Trade-offs: Complexity