TrochtaOndrej
df0baeff36
Tracked: CLAUDE.md, agents, skills, settings, memory. Ephemeral data (sessions, history, telemetry, tasks) excluded via .gitignore. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
1.8 KiB
1.8 KiB
name, description, argument-hint, allowed-tools
| name | description | argument-hint | allowed-tools | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| full-cycle | Full development cycle - branch, implement, review, fix, test, merge to dev | <task-description> |
|
Full Development Cycle
Execute a complete development cycle for the given task: $ARGUMENTS
Workflow Steps
1. Branch
- Create a feature/fix branch from
dev:git checkout dev && git pull && git checkout -b <type>/<short-name> - Branch naming:
feature/for new features,fix/for bug fixes,refactor/for refactoring
2. Investigate
- Read CLAUDE.md and relevant codebase files
- Understand the current architecture and patterns
- Identify all files that need changes
3. Implement
- Make the necessary code changes
- Follow project conventions from CLAUDE.md (primary constructors, file-scoped namespaces, XML docs)
- Keep changes minimal and focused
4. Build & Verify
- Run
dotnet build OTCryptoRobot.sln- must have 0 errors - Check for new warnings in changed files
5. Self-Review
- Review all changes with
git diff - Check for: security issues, missing null checks, async/await correctness, proper error handling
- Fix any issues found
6. Test (if applicable)
- Run relevant tests:
dotnet test - If services need restart, use systemctl --user restart
7. Commit & Merge
- Stage specific files (not
git add -A) - Write descriptive commit message with Co-Authored-By
- Merge to dev:
git checkout dev && git merge <branch> --ff-only - Delete feature branch:
git branch -d <branch>
Important Rules
- Never push to remote without explicit user request
- Never use --force or --no-verify
- If build fails, fix and create NEW commit (don't amend)
- All I/O must be async, all public members need XML docs