mosdat

Plugin mosdat in jeanfbrito/mOSdat. Commands read from the repo's manifest — 20 days ago.

Skills (11)

• gitnexus-cli

  Use when the user needs to run GitNexus CLI commands like analyze/index a repo, check status, clean the index, generate a wiki, or list indexed repos. Examples: \"Index this repo\", \"Reanalyze the codebase\", \"Generate a wiki\"

• gitnexus-debugging

  Use when the user is debugging a bug, tracing an error, or asking why something fails. Examples: \"Why is X failing?\", \"Where does this error come from?\", \"Trace this bug\"

• gitnexus-exploring

  Use when the user asks how code works, wants to understand architecture, trace execution flows, or explore unfamiliar parts of the codebase. Examples: \"How does X work?\", \"What calls this function?\", \"Show me the auth flow\"

• gitnexus-guide

  Use when the user asks about GitNexus itself — available tools, how to query the knowledge graph, MCP resources, graph schema, or workflow reference. Examples: \"What GitNexus tools are available?\", \"How do I use GitNexus?\"

• gitnexus-impact-analysis

  Use when the user wants to know what will break if they change something, or needs safety analysis before editing code. Examples: \"Is it safe to change X?\", \"What depends on this?\", \"What will break?\"

• gitnexus-refactoring

  Use when the user wants to rename, extract, split, move, or restructure code safely. Examples: \"Rename this function\", \"Extract this into a module\", \"Refactor this class\", \"Move this to a separate file\"

• mosdat-authoring

  Use when authoring mOSdat scenarios for a new feature. Walks the routines-first workflow: identify atomic interactions, reuse or create routines, compose scenario. Triggers on /mosdat-authoring, 'write tests for X in mOSdat', 'author scenario for X', 'add mOSdat coverage for PR #N'.

• mosdat-insight

  Use when the user invokes /insight, says 'capture insight', or after repeated failures to surface relevant project and personal lessons. Captures structured insight entries and surfaces existing knowledge to prevent repeated mistakes.

• mosdat-pr-preflight

  Force a binary-freshness check before any PR-scoped mosdat scenario. Triggers on "test PR N", "run 3325-*", "rodar <PR>-*". Refuses to skip the build+deploy+asar-verify step — stale binaries produce false-negative scenario failures that look like framework bugs.

• mosdat-qa-pr-status-comment

  Update or create a GitHub PR comment that reports the current mOSdat QA-flow status per configured OS target. Use when asked to post, refresh, or show the actual QA matrix state for PR tests, including which systems are passing or still failing.

• mosdat-testing

  Use whenever validating a real desktop/Electron app change against a real machine is relevant — testing a Rocket.Chat.Electron PR, checking whether a build actually launches and works on Windows/Linux, driving UI interactions on a VM, or answering "does this PR/build work" / "can you verify this on