Run any Skill in Manus with one click

symptomsync-doc-sync

Stars29

Forks8

UpdatedFebruary 28, 2026 at 02:43

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.

Installation

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.

Run Skill in Manus

Source

hoangsonww

hoangsonww/SymptomSync-Health-App

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

File Explorer

3 files

SKILL.md

readonly

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.

SymptomSync Doc Sync

Use this skill when code and docs may have drifted.

Workflow

Identify which behavior changed and which docs mention it.
Verify the current behavior from code before editing prose.
Update only the documents that are now stale.
Keep claims concrete; avoid marketing language when operational details are the point.

Main doc targets

README.md
ARCHITECTURE.md
DEPLOYMENTS.md
docs/DESIGN.md
jenkins/README.md
devops/runbooks/progressive-delivery.md
devops/runbooks/production-readiness.md

Read references/doc-map.md when you need the doc-to-code mapping.

Guardrails

Prefer code-backed statements over aspirational language.
If timing, schedules, or rollout behavior matters, trust the checked-in code and SQL over older prose docs.
Update the narrowest stale document set rather than rewriting everything.

Related skills

Use the area-specific skill first if the change is in web, data, agentic AI, or release infrastructure.
Use $symptomsync-review if you want to review for drift instead of editing it.

More from this repository

same repository

symptomsync-agentic-ai-change

hoangsonww/SymptomSync-Health-App

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.

2026-02-2829

symptomsync-data-change

hoangsonww/SymptomSync-Health-App

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.

2026-02-2829

symptomsync-release-change

hoangsonww/SymptomSync-Health-App

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.

2026-02-2829

symptomsync-review

hoangsonww/SymptomSync-Health-App

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.

2026-02-2829

symptomsync-web-change

hoangsonww/SymptomSync-Health-App

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.

2026-02-2829

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.

SymptomSync Doc Sync

Use this skill when code and docs may have drifted.

Workflow

Identify which behavior changed and which docs mention it.
Verify the current behavior from code before editing prose.
Update only the documents that are now stale.
Keep claims concrete; avoid marketing language when operational details are the point.

Main doc targets

README.md
ARCHITECTURE.md
DEPLOYMENTS.md
docs/DESIGN.md
jenkins/README.md
devops/runbooks/progressive-delivery.md
devops/runbooks/production-readiness.md

Read references/doc-map.md when you need the doc-to-code mapping.

Guardrails

Prefer code-backed statements over aspirational language.
If timing, schedules, or rollout behavior matters, trust the checked-in code and SQL over older prose docs.
Update the narrowest stale document set rather than rewriting everything.

Related skills

Use the area-specific skill first if the change is in web, data, agentic AI, or release infrastructure.
Use $symptomsync-review if you want to review for drift instead of editing it.