القائمة
Reconcile the wiki with the current code. Detects where the implementation has diverged from the wiki and updates the wiki pages (or flags the divergence for a decision). Use after significant code changes, or when the PostToolUse reminder fires, or when the user asks to "sync the wiki".
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | wiki-sync |
| description | Reconcile the wiki with the current code. Detects where the implementation has diverged from the wiki and updates the wiki pages (or flags the divergence for a decision). Use after significant code changes, or when the PostToolUse reminder fires, or when the user asks to "sync the wiki". |
| disable-model-invocation | false |
The wiki is the source of truth — but implementation sometimes reveals that the wiki was wrong, incomplete, or has been outgrown. This skill closes that gap deliberately, so the wiki stays trustworthy.
Read wiki/INDEX.md and the pages relevant to the area that changed.
requirements.md, architecture.md, the affected wiki/specs/ pages). Look for:
behaviour the code has that the wiki does not describe; wiki statements the code no
longer satisfies; structural drift from architecture.md; rule drift — a rule in
architecture.md's Rules section whose linked decision is missing or superseded/
abandoned, a standing-constraint decision in decisions.md with no matching rule, or
code that violates a binding rule.wiki/decisions.md and update the affected pages.INDEX.md if pages were added or restructured.Primary entry point for a freshly cloned Vibin seed repo. Interviews the user about the project, stack, package manager, constraints, and initial backlog, populates the wiki/ starter pages, scaffolds the chosen stack, writes the stack-specific permission profile, and hands off to the manager skill. Use when starting a new project, or when the user says "bootstrap", "set up the project", or "let's begin".
File a new work item into wiki/backlog/inbox/. Use whenever the user reports a bug, asks for a feature, or proposes a change of direction mid-run — instead of inline-patching. Any agent (including subagents) can invoke this. Triggered by /intake "<title>" or when an agent recognises new work that should be captured.
One-question-at-a-time interviewing discipline that drives /bootstrap and /intake to ~95% confidence before writing the wiki or an item card. Use when gathering requirements for a new project or fleshing out a vague work item.
Orchestrates Vibin's wiki-driven, spec-driven, test-first build pipeline. The top-level session runs this skill to order the backlog and drive the spec-writer -> test-writer -> implementer -> reviewer pipeline (or the bug / research / chore tracks), one item at a time. Use after /bootstrap, or to resume building the backlog.
Bring an existing Vibin project up to date with the latest seed by diffing the project's recorded seed commit against the latest Vibin on GitHub and applying the changes. Use when the user says "migrate", "migrate-vibin", "upgrade Vibin", "apply the latest seed changes", or after a new seed release. Reads the seed commit hash from .vibin-version, audits the project's actual state, applies the migrations added since, and reconciles seed-owned files while preserving local customizations.
Reference for the red-green-refactor test-first discipline used by the test-writer and implementer agents. Use when you need the canonical explanation of how Vibin's tests-first workflow works, or to settle a question about test ordering, "minimum" code, or trivially-passing tests.