mirror of
https://github.com/harivansh-afk/evaluclaude-harness.git
synced 2026-04-19 20:00:46 +00:00
analyze
This commit is contained in:
parent
4b24606d0e
commit
9297f0b1ee
13 changed files with 1292 additions and 16 deletions
35
prompts/analyzer-user.md
Normal file
35
prompts/analyzer-user.md
Normal file
|
|
@ -0,0 +1,35 @@
|
|||
# Codebase Analysis Request
|
||||
|
||||
## Repository Summary
|
||||
|
||||
```json
|
||||
{{REPO_SUMMARY}}
|
||||
```
|
||||
|
||||
## Analysis Focus
|
||||
|
||||
{{FOCUS_INSTRUCTIONS}}
|
||||
|
||||
## Instructions
|
||||
|
||||
1. Review the module exports, focusing on:
|
||||
- Functions with signatures (testable interfaces)
|
||||
- Classes with methods
|
||||
- High-complexity modules
|
||||
|
||||
2. For each testable target, generate scenarios covering:
|
||||
- Happy path (normal operation)
|
||||
- Edge cases (empty, null, boundary values)
|
||||
- Error paths (exceptions, invalid inputs)
|
||||
|
||||
3. Use AskUserQuestion if you need clarification about:
|
||||
- Business logic requirements
|
||||
- Expected behavior for ambiguous cases
|
||||
- Priority of specific modules
|
||||
|
||||
4. Generate the EvalSpec JSON with {{MAX_SCENARIOS}} scenarios maximum.
|
||||
|
||||
5. Prioritize:
|
||||
- Most active files (by git history)
|
||||
- Functions with docstrings (clearer intent)
|
||||
- Public exports over internal helpers
|
||||
Loading…
Add table
Add a link
Reference in a new issue