// Workflow for keeping SymptomSync's checked-in docs aligned with implementation. Use when changes alter behavior described in README.md, ARCHITECTURE.md, DEPLOYMENTS.md, docs/, jenkins/README.md, or devops/runbooks/, or when a task is specifically about reconciling documentation with the current code.
Guide for changing SymptomSync's Python symptom-analysis service under agentic_ai/. Use when tasks touch the FastAPI service, LangGraph flow, agents, chains, settings, tests, monitoring, or deployment configuration for the agentic_ai workspace.
Guide for changing SymptomSync SQL, schema contracts, and reminder plumbing safely. Use when tasks touch supabase/, database/, database/migrations/, SQL functions, cron/reminder logic, user_notifications behavior, mirrored schema maintenance, or frontend code that depends on those contracts.
Guide for making safe changes to SymptomSync infrastructure, CI/CD, deployment, and operational behavior. Use when tasks touch aws/, ansible/, jenkins/, devops/, Dockerfile, .devcontainer/, or .github/workflows/ci.yml, especially for CDK stack changes, blue-green rollout logic, canary deployment behavior, pipeline changes, or production-readiness docs.
Repo-specific review workflow for SymptomSync. Use when reviewing code, plans, or diffs across frontend, SQL, AI service, infrastructure, or CI/CD so the review reflects this repository's real failure modes such as mirrored SQL drift, weak frontend test wiring, doc-vs-code mismatches, config regressions, and unsafe release changes.
Guide for making safe, repo-specific changes in SymptomSync's Next.js frontend under web/. Use when tasks touch pages-router pages, React components, Supabase client flows, Gemini chat UX, charts, calendar behavior, uploads, auth screens, or frontend-facing API routes such as pages/api/med.ts.
| name | symptomsync-doc-sync |
| description | Workflow for keeping SymptomSync's checked-in docs aligned with implementation. Use when changes alter behavior described in README.md, ARCHITECTURE.md, DEPLOYMENTS.md, docs/, jenkins/README.md, or devops/runbooks/, or when a task is specifically about reconciling documentation with the current code. |
Use this skill when code and docs may have drifted.
README.mdARCHITECTURE.mdDEPLOYMENTS.mddocs/DESIGN.mdjenkins/README.mddevops/runbooks/progressive-delivery.mddevops/runbooks/production-readiness.mdRead references/doc-map.md when you need the doc-to-code mapping.
$symptomsync-review if you want to review for drift instead of editing it.