mirror of
https://github.com/harivansh-afk/veet-code.git
synced 2026-04-17 15:04:56 +00:00
update to allow claude command access
This commit is contained in:
parent
b3fbb0faff
commit
05d86562ee
7 changed files with 122 additions and 14 deletions
40
.claude/commands/veet-add-tests.md
Normal file
40
.claude/commands/veet-add-tests.md
Normal file
|
|
@ -0,0 +1,40 @@
|
|||
---
|
||||
description: Add more test cases to an existing problem
|
||||
argument-hint: [problem-name]
|
||||
allowed-tools: Read, Edit
|
||||
---
|
||||
|
||||
# Add More Test Cases
|
||||
|
||||
Add additional test cases to an existing problem to make it more challenging or cover more edge cases.
|
||||
|
||||
## Problem
|
||||
Problem name: $ARGUMENTS (if empty, ask which problem)
|
||||
|
||||
## Process
|
||||
|
||||
1. Read the existing solution.py and tests.py for the problem
|
||||
2. Analyze what edge cases are NOT covered
|
||||
3. Ask the user what kind of tests they want:
|
||||
- Edge cases (empty, single element, boundaries)
|
||||
- Performance tests (large inputs)
|
||||
- Tricky cases (duplicates, negative numbers, special characters)
|
||||
- Custom scenario they describe
|
||||
|
||||
4. Add new test functions to tests.py using the Edit tool
|
||||
|
||||
## Test naming convention
|
||||
```python
|
||||
def test_edge_case_{description}():
|
||||
"""Clear description of what this tests."""
|
||||
...
|
||||
|
||||
def test_tricky_{description}():
|
||||
"""Description of the tricky scenario."""
|
||||
...
|
||||
```
|
||||
|
||||
## Do NOT:
|
||||
- Remove existing tests
|
||||
- Modify the solution.py
|
||||
- Add tests that are impossible given the constraints
|
||||
Loading…
Add table
Add a link
Reference in a new issue