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

Mar 25, 2026

Productivity

PromptBeginner5 minmarkdown

- Recency bias: Treating the most recent publication as automatically more authoritative without evaluating whether it supersedes

contradicts

Mar 25, 2026

Productivity

PromptBeginner5 minmarkdown

- Identify potential conflicts of interest including funding sources

organizational affiliations

Mar 25, 2026

Productivity

PromptBeginner5 minmarkdown

- Assign each task a stable ID (e.g.

TASK-1.1) and use checklist items in outputs.

Mar 25, 2026

Productivity

PromptBeginner5 minmarkdown

- Treat every requirement below as an explicit

trackable task.

Mar 25, 2026

Coding & Debugging

PromptBeginner5 minmarkdown

RULE: When using this prompt

you must create a file named `TODO_bug-risk-analyst.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,wka...

Mar 25, 2026

Coding & Debugging

PromptBeginner5 minmarkdown

- Remediation: Specific code fix

configuration change

Mar 25, 2026

Coding & Debugging

PromptBeginner5 minmarkdown

- Scope: Code paths

modules

Mar 25, 2026

Find agent skills by outcome

- The target consumers of the index (other agents

- **Sensitive data in index**: Credentials

- Map the public API surface with all exported functions

- Identify code paths with no error handling

- Automate re-indexing triggers via git hooks

- Find OpenAPI/Swagger specifications

- Prioritize inclusion of entry points

- Omit generated code

- Ensure no sensitive data (secrets

- Document API routes

- Trace module boundaries by identifying package exports

- Run parallel glob searches across the five focus areas: source code

- **Scan** repository directory structures across all focus areas (source code

- Assign each task a stable ID (e.g.

You are a senior codebase analysis expert and specialist in repository indexing

- Treat every requirement below as an explicit

**RULE:** When using this prompt

- **Recency bias**: Treating the most recent publication as automatically more authoritative without evaluating whether it supersedes

- Identify potential conflicts of interest including funding sources

- Assign each task a stable ID (e.g.

- Treat every requirement below as an explicit

**RULE:** When using this prompt

- **Remediation**: Specific code fix

- **Scope**: Code paths

- Sensitive data in index: Credentials

- Scan repository directory structures across all focus areas (source code

RULE: When using this prompt

- Recency bias: Treating the most recent publication as automatically more authoritative without evaluating whether it supersedes

RULE: When using this prompt

- Remediation: Specific code fix

- Scope: Code paths