Replace requirements.txt to pyproject.toml

Author: nsyzrantsev

.claude/commands/commit-push-pr.md

@@ -0,0 +1,40 @@
+# Commit, Push, and Create PR
+
+Automates the commit, push, and PR creation workflow.
+
+## Context
+
+```bash
+# Current git status
+git status --porcelain
+
+# Current branch
+git branch --show-current
+
+# Recent commits for style reference
+git log --oneline -5
+```
+
+## Instructions
+
+1. Review the git status output above to understand what changed
+2. Stage all relevant changes (excluding any sensitive files like .env)
+3. Create a conventional commit message following the project style:
+   - `feat:` for new features
+   - `fix:` for bug fixes
+   - `chore:` for maintenance
+   - `docs:` for documentation
+   - `refactor:` for refactoring
+   - Use scope when applicable: `feat(asr):`, `fix(storage):`
+4. Push to the remote branch
+5. Create a PR with:
+   - Clear title matching the commit message
+   - Summary section with 1-3 bullet points
+   - Test plan section
+   - Reference to any related issues using "Fixes #N" or "Relates to #N"
+
+## Arguments
+
+- `$ARGUMENTS` - Optional: PR title override or commit message
+
+If no arguments provided, generate appropriate messages from the changes.

.claude/commands/commit-push.md

@@ -0,0 +1,29 @@
+# Commit and Push
+
+Automates the commit and push.
+
+## Context
+
+```bash
+# Current git status
+git status --porcelain
+
+# Current branch
+git branch --show-current
+
+# Recent commits for style reference
+git log --oneline -5
+```
+
+## Instructions
+
+1. Review the git status output above to understand what changed
+2. Stage all relevant changes (excluding any sensitive files like .env)
+3. Create a conventional commit message following the project style:
+   - `feat:` for new features
+   - `fix:` for bug fixes
+   - `chore:` for maintenance
+   - `docs:` for documentation
+   - `refactor:` for refactoring
+   - Use scope when applicable: `feat(api):`, `fix(auth):`
+4. Push to the remote branch

.claude/commands/format-code.md

@@ -0,0 +1,37 @@
+# Format Code
+
+Format and lint code according to project standards.
+
+## Context
+
+```bash
+# Check for modified Python files
+git diff --name-only --diff-filter=ACMR | grep -E '\.py$' || echo "No Python files modified"
+
+# Check ruff version
+uv run ruff --version
+```
+
+## Instructions
+
+1. Run the formatting tools in order:
+   - `just format` - Auto-format with ruff
+   - `just lint` - Check for remaining issues
+   - `just type` - Run type checker
+
+2. For any issues that can't be auto-fixed:
+   - List the file and line number
+   - Explain the issue
+   - Suggest a fix
+
+3. After formatting, show:
+   - Files that were modified
+   - Any remaining issues that need manual attention
+
+## Arguments
+
+- `$ARGUMENTS` - Optional: specific files or directories to format
+  - Example: `flows/vibyy_asr/`
+  - Example: `common/storage/client.py`
+
+If no arguments, format all modified files.

.claude/commands/review-pr.md

@@ -0,0 +1,62 @@
+# Review PR
+
+Review a pull request with parallel subagents for comprehensive analysis.
+
+## Context
+
+```bash
+# Get PR info if number provided
+if [ -n "$ARGUMENTS" ]; then
+  gh pr view "$ARGUMENTS" --json title,body,files,additions,deletions 2>/dev/null || echo "PR not found"
+fi
+
+# Current branch diff if no PR number
+git diff main...HEAD --stat 2>/dev/null || git diff origin/main...HEAD --stat
+```
+
+## Instructions
+
+Review the PR using multiple perspectives:
+
+1. **Style Check**: Verify code follows CONTRIBUTING.md guidelines
+   - Naming conventions (flow_vibyy_*, task_*, UPPER_SNAKE_CASE)
+   - Import style (absolute imports, isort grouping)
+   - Line length (120 chars), quote style (single quotes)
+   - Type hints on all functions
+
+2. **Bug Hunt**: Look for common issues
+   - Unhandled exceptions
+   - Resource leaks (unclosed files/connections)
+   - Missing null checks
+   - Logic errors in conditionals
+
+3. **Security Review**: Check for vulnerabilities
+   - Hardcoded credentials or secrets
+   - SQL/command injection risks
+   - Unsafe deserialization
+   - Missing input validation
+
+4. **Architecture**: Evaluate design
+   - Does it follow existing patterns?
+   - Is it over-engineered?
+   - Are there simpler alternatives?
+
+5. **Tests**: Verify test coverage
+   - Are new functions tested?
+   - Are edge cases covered?
+   - Do tests follow naming conventions?
+
+## Arguments
+
+- `$ARGUMENTS` - Optional: PR number to review
+  - Example: `42`
+
+If no PR number, review the current branch's diff against main.
+
+## Output Format
+
+Provide findings grouped by severity:
+- **Critical**: Must fix before merge
+- **Major**: Should fix, can discuss
+- **Minor**: Nice to have improvements
+- **Praise**: Things done well

.claude/commands/run-tests.md

@@ -0,0 +1,36 @@
+# Run Tests
+
+Run the project test suite with proper formatting.
+
+## Context
+
+```bash
+# Check if test dependencies are installed
+uv run python -c "import pytest" 2>&1 || echo "pytest not installed"
+```
+
+## Instructions
+
+1. Run the full quality gate suite:
+   - `just lint` - Run ruff linter
+   - `just format` - Auto-format code
+   - `just type` - Run type checker
+   - `just tests-unit` - Run unit tests
+
+2. If any step fails:
+   - Show the specific errors clearly
+   - Suggest fixes if obvious
+   - Do NOT proceed to the next step
+
+3. Report summary at the end:
+   - Total tests run
+   - Tests passed/failed
+   - Any warnings or issues
+
+## Arguments
+
+- `$ARGUMENTS` - Optional: specific test path or pattern
+  - Example: `tests/unit/test_storage.py`
+  - Example: `tests/unit/test_storage.py::test_upload`
+
+If arguments provided, run only those specific tests after linting.

.github/workflows/docker-multiarch.yml .github/workflows/cd.yml.github/workflows/docker-multiarch.yml renamed to .github/workflows/cd.yml

@@ -1,4 +1,4 @@
-name: Continuous Deployment (Docker multi-arch)
+name: Continuous Deployment (build & push docker images)
 
 on:
   push: