Claude Code Configuration

Project Setup

IMPORTANT: Before starting any work on a repository:

Check for a CLAUDE.md file in the repository root
Check for a CLAUDE.md file in parent directories (we often work across repos on localhost)
Read and follow all instructions in those files
These project-specific instructions override default Claude Code behavior
Look for conventions around commits, testing, code style, and workflows
If working across multiple repositories, respect the conventions from each repo's CLAUDE.md

Commit Attribution

When creating git commits, use clean, simple commit messages:

Commit message here.

Do NOT include:

🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
Any fake corporate entities as co-authors

Only attribute real humans as co-authors when collaborating.

Database Migrations (Alembic)

When adding new columns or modifying the database schema:

Backup SQLite first: cp data/remarkbox.sqlite data/remarkbox.sqlite.bak
Add the column to the model in remarkbox/models/
Generate migration: alembic -c development.ini revision --autogenerate -m "description"
Clean up migration: Remove extra autogenerated changes, keep only the new field
Run migration: alembic -c development.ini upgrade head

Production Troubleshooting

For read-only troubleshooting on production, use tmux-hosts:

tmux-hosts

Important: This is for read-only investigation only. Do not make changes to production systems.

Deployment Status

Check GitLab pipeline status after pushing:

# Get pipeline status via API (replace PIPELINE_ID)
curl -s "https://git.unturf.com/api/v4/projects/engineering%2Fremarkbox%2Fremarkbox/pipelines/PIPELINE_ID"

# Or view in browser:
# https://git.unturf.com/engineering/remarkbox/remarkbox/-/pipelines

The pipeline status will show "status":"success" when deployment is complete.

2 KiB Raw Blame History