Menu
Use when working on `save_it` local development, setup, dev server startup, local checks, Typesense migrations, or code submission workflow.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | save-it-development |
| description | Use when working on `save_it` local development, setup, dev server startup, local checks, Typesense migrations, or code submission workflow. |
| metadata | {"short-description":"save_it development workflow"} |
Use this skill for routine development work in the save_it repository.
If the current checkout is a git worktree and this project has not completed setup yet, run worktree init skill first, then run the full setup below.
Run from the repository root:
mise trust
mise install
mix setup
If mise.toml is missing in the current directory, move to the parent directory and retry the mise commands.
Start dependencies:
docker compose up
After startup:
http://localhost:8108/healthhttp://localhost:3000test@example.com / pass123456Run the bot:
export TELEGRAM_BOT_TOKEN=<YOUR_TELEGRAM_BOT_TOKEN>
mix dev
Reset local Docker services and runtime data from the repository root:
docker compose down --volumes
mix reset
Prefer the smallest relevant check for the change:
mix test
mix format
mix credo --strict
mix dialyzer
mix checks
mix checks is the common check-only suite and must not rewrite files.
Typesense schema changes live under priv/typesense/migrations/ as ordered up/down migration files. Use mix tasks instead of legacy ad-hoc runner scripts:
mix ts.migrate
mix ts.rollback
mix ts.rollback 20260524000000
mix ts.reset
feat:, fix:, chore:, ci:, refactor:, or performance:.git cz --non-interactive --disable-emoji
gh for GitHub operations.Use Docker Compose to build and run the acceptance environment for `save_it`.
Prepare, verify, and publish `save_it` releases by updating `mix.exs`, creating the release commit and tag, and publishing a GitHub release. Use when the user asks to cut a stable release, prepare a prerelease, or verify release readiness for this repository. This repository uses CalVer `YYYY.M.D` for stable releases and prerelease tags such as `YYYY.M.D-rc.N`.
Maintain the save_it repository CHANGELOG.md using Keep a Changelog 1.1.0 with CalVer version headings. Use at the end of repository work, before final response or commit/PR handoff, when user-facing product behavior, features, fixes, removals, security changes, or breaking changes changed.