بنقرة واحدة
docs-sync
Use when changing README, README_ja, requirements, ADRs, or user-facing behavior.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
القائمة
Use when changing README, README_ja, requirements, ADRs, or user-facing behavior.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use before committing, pushing, or opening a PR to catch missing files, mixed staging, validation gaps, and PR metadata mistakes.
Use when drafting public announcements, articles, marketplace copy, Hugging Face/ModelScope notes, or English replies.
Use when changing ComfyUI node classes, schemas, inputs, outputs, metadata, or registration.
Use when checking OpenCV/Kornia/ComfyUI dependencies, import failures, pyproject metadata, or environment-specific behavior.
Use before version bumps, Comfy Registry publishing, release PRs, tags, or public release notes.
Use when changing Classic/Flow motion estimation, OpenCV backend selection, fallback behavior, or stabilization math.
| name | docs-sync |
| description | Use when changing README, README_ja, requirements, ADRs, or user-facing behavior. |
Use this skill when behavior, schema, dependencies, workflow samples, or release metadata changes.
README.md and README_ja.md should describe the same public behavior.docs/requirements/ should state the intended behavior and acceptance criteria.docs/adr/ should record significant design decisions, especially compatibility
or fallback changes.pyproject.toml version/dependencies should match release and runtime behavior.python3 scripts/validate_repo.py