chore(deps): bump actions/setup-python from 5 to 6

.agents/skills/docker-flask-postgres-api/SKILL.md

@@ -0,0 +1,121 @@
+```markdown
+# docker-flask-postgres-api Development Patterns
+
+> Auto-generated skill from repository analysis
+
+## Overview
+
+This skill teaches the core development patterns, coding conventions, and workflows used in the `docker-flask-postgres-api` repository. The repository is a Python-based API project, using Docker for deployment and PostgreSQL as the database backend. It emphasizes clear commit messages, modular code organization, and robust testing and documentation practices.
+
+## Coding Conventions
+
+- **File Naming:**  
+  Use camelCase for file names.  
+  _Example:_  
+  ```
+  userRoutes.py
+  dbConnection.py
+  ```
+
+- **Import Style:**  
+  Use relative imports within the package.  
+  _Example:_  
+  ```python
+  from .schemas import UserSchema
+  from .utils import validate_input
+  ```
+
+- **Export Style:**  
+  Use named exports (explicitly define what is exported).  
+  _Example:_  
+  ```python
+  def create_user(...):
+      ...
+
+  def delete_user(...):
+      ...
+  ```
+
+- **Commit Messages:**  
+  Follow [Conventional Commits](https://www.conventionalcommits.org/) with prefixes: `fix`, `docs`, `feat`, `test`.  
+  _Example:_  
+  ```
+  feat: add user registration endpoint with validation
+  fix: correct db connection string parsing
+  docs: update README with setup instructions
+  test: add tests for user login route
+  ```
+
+## Workflows
+
+### Feature Development: API Endpoint
+**Trigger:** When adding a new API endpoint with validation, error handling, and tests  
+**Command:** `/new-endpoint`
+
+1. **Implement endpoint logic** in `app/__init__.py`  
+   _Example:_  
+   ```python
+   @app.route('/users', methods=['POST'])
+   def create_user():
+       # Endpoint logic here
+   ```
+2. **Add or update validation** in `app/schemas.py`  
+   _Example:_  
+   ```python
+   class UserSchema(Schema):
+       username = fields.Str(required=True)
+       email = fields.Email(required=True)
+   ```
+3. **Write or update tests** in `tests/test_routes.py`  
+   _Example:_  
+   ```python
+   def test_create_user(client):
+       response = client.post('/users', json={...})
+       assert response.status_code == 201
+   ```
+4. **Update documentation** in `README.md`  
+   - Document the new endpoint, request/response examples, and any new environment variables.
+
+---
+
+### Documentation Update
+**Trigger:** When documenting new features, configuration, or operational procedures  
+**Command:** `/update-docs`
+
+1. **Update environment variable documentation** in `.env.example`  
+   - Add or update variables relevant to the new feature.
+2. **Update main documentation** in `README.md`  
+   - Describe new features, configuration steps, or architectural changes.
+
+---
+
+## Testing Patterns
+
+- **Test File Naming:**  
+  Test files follow the pattern `*.test.*` (e.g., `userRoutes.test.py`).
+
+- **Test Location:**  
+  Tests are placed in the `tests/` directory, commonly in files like `tests/test_routes.py`.
+
+- **Test Structure:**  
+  Each test function typically uses a client fixture to make HTTP requests to endpoints and asserts on the response.
+
+  _Example:_  
+  ```python
+  def test_get_users(client):
+      response = client.get('/users')
+      assert response.status_code == 200
+      assert isinstance(response.json, list)
+  ```
+
+- **Testing Framework:**  
+  The specific framework is not detected, but typical Python test frameworks (like `pytest`) are likely used.
+
+## Commands
+
+| Command        | Purpose                                                         |
+|----------------|-----------------------------------------------------------------|
+| /new-endpoint  | Start the workflow to add a new API endpoint with tests & docs  |
+| /update-docs   | Start the workflow to update documentation and environment vars |
+
+```

.agents/skills/docker-flask-postgres-api/agents/openai.yaml

@@ -0,0 +1,6 @@
+interface:
+  display_name: "Docker Flask Postgres Api"
+  short_description: "Repo-specific patterns and workflows for docker-flask-postgres-api"
+  default_prompt: "Use the docker-flask-postgres-api repo skill to follow existing architecture, testing, and workflow conventions."
+policy:
+  allow_implicit_invocation: true

.claude/commands/documentation-update.md

@@ -0,0 +1,35 @@
+---
+name: documentation-update
+description: Workflow command scaffold for documentation-update in docker-flask-postgres-api.
+allowed_tools: ["Bash", "Read", "Write", "Grep", "Glob"]
+---
+
+# /documentation-update
+
+Use this workflow when working on **documentation-update** in `docker-flask-postgres-api`.
+
+## Goal
+
+Updates documentation files to reflect new features, environment variables, or architectural changes.
+
+## Common Files
+
+- `.env.example`
+- `README.md`
+
+## Suggested Sequence
+
+1. Understand the current state and failure mode before editing.
+2. Make the smallest coherent change that satisfies the workflow goal.
+3. Run the most relevant verification for touched files.
+4. Summarize what changed and what still needs review.
+
+## Typical Commit Signals
+
+- Update environment variable documentation in .env.example
+- Update main documentation in README.md
+
+## Notes
+
+- Treat this as a scaffold, not a hard-coded script.
+- Update the command if the workflow evolves materially.

.claude/commands/feature-development-api-endpoint.md

@@ -0,0 +1,39 @@
+---
+name: feature-development-api-endpoint
+description: Workflow command scaffold for feature-development-api-endpoint in docker-flask-postgres-api.
+allowed_tools: ["Bash", "Read", "Write", "Grep", "Glob"]
+---
+
+# /feature-development-api-endpoint
+
+Use this workflow when working on **feature-development-api-endpoint** in `docker-flask-postgres-api`.
+
+## Goal
+
+Implements a new API endpoint, including code, tests, and documentation.
+
+## Common Files
+
+- `app/__init__.py`
+- `app/schemas.py`
+- `tests/test_routes.py`
+- `README.md`
+
+## Suggested Sequence
+
+1. Understand the current state and failure mode before editing.
+2. Make the smallest coherent change that satisfies the workflow goal.
+3. Run the most relevant verification for touched files.
+4. Summarize what changed and what still needs review.
+
+## Typical Commit Signals
+
+- Implement endpoint logic in app/__init__.py
+- Add or update validation in app/schemas.py
+- Write or update tests in tests/test_routes.py
+- Update documentation in README.md
+
+## Notes
+
+- Treat this as a scaffold, not a hard-coded script.
+- Update the command if the workflow evolves materially.