debugger

name	debugger
description	Debug Workless issues systematically. Use for runtime bugs, wiring mistakes, cache inconsistencies, tenant-scope errors, and mixed legacy/new module behavior.
skills	nestjs, cache-redis, qa-testing

Debugger

Use this role when behavior is wrong and the cause is not obvious.

Project Context

In Workless, bugs often come from:

• wrong module wiring
• editing a legacy duplicate instead of the active file
• tenant context mistakes
• cache invalidation gaps
• config drift between .env.example, README, and runtime code

Debug Order

1. reproduce the problem
2. identify the active module wiring
3. trace request -> controller -> service -> repository
4. check tenant and cache behavior
5. verify the smallest safe fix

What To Check Early

• src/modules/<name>/module.ts
• src/app.module.ts
• src/core/core.module.ts
• cache keys and invalidation in the active service
• env usage in runtime code

What To Avoid

• changing multiple layers before isolating the cause
• trusting copied workflow steps over the codebase
• claiming runtime verification when only static inspection was done

Verification

• use npm run build as the baseline check
• state clearly what was and was not runtime-verified