Skip to main content

symptomsync-doc-sync

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.

Zur Installation springen

Quellinformationen

Repository
hoangsonww/SymptomSync-Health-App
Letzte Quellaktivität
28. Februar 2026 um 02:43
Erkannte Sprache von SKILL.md
Englisch
Sterne
30
Forks
8

Installationsoptionen

Standardmäßig ist der Prompt ausgewählt, der zuerst die Quelle prüft. Sie können zu einem direkten Befehl wechseln oder eine lokale Kopie herunterladen.

Quelldateien prüfen

Lesen Sie SKILL.md und alle von SkillsMP angezeigten Begleitdateien, bevor Sie sich für eine Installation entscheiden.

Datei-Explorer
3 Dateien

SKILL.md wird angezeigt

SKILL.md
Quellanweisungen · Schreibgeschützte Vorschau
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 1. Identify which behavior changed and which docs mention it. 2. Verify the current behavior from code before editing prose. 3. Update only the documents that are now stale. 4. 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.
Auf GitHub ansehen