القائمة
Refresh MoonMind services from git by fetching and pinning a branch snapshot, pulling compose images, then restarting changed containers with optional orchestrator inclusion.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | update-moonmind |
| description | Refresh MoonMind services from git by fetching and pinning a branch snapshot, pulling compose images, then restarting changed containers with optional orchestrator inclusion. |
| metadata | {"required-capabilities":["git","docker"]} |
repo (optional): Path to the MoonMind git repository. Default ..branch (optional): Branch to update from. Default main.allowDirty / allow_dirty (optional): Allow running with uncommitted local git changes.noComposePull / no_compose_pull (optional): Skip pulling updated Docker images.dryRun / dry_run (optional): Print commands without executing them.restartOrchestrator / restart_orchestrator (optional): Restart the orchestrator container too.bash .agents/skills/update-moonmind/scripts/run-update-moonmind.sh --repo <path> --branch <branch>.
--restart-orchestrator if you need the orchestrator container restarted as well.branch as a safe git branch valuegit fetch <branch> from origin<branch> to the exact commit captured by that fetchdocker compose pull while the resolver worker remains quiesced
(unless noComposePull is set)orchestrator container, even when it changed.Discover open Dependabot version-bump PRs and enqueue one `pr-resolver` workflow for each.
Provide the shared fan-out engine used by provider-specific Jira and GitHub batch presets to enqueue child workflows with inherited runtime and stable evidence.
Master orchestrator to resolve a PR by diagnosing state and delegating to specialized skills.
Verify a GitHub issue against the current repository state, then post a GitHub issue comment with a PASS, PARTIAL, FAIL, or BLOCKED verdict. Works in two modes: (a) feature-branch mode, comparing a checked-out branch to its base ref; or (b) main/trunk mode, verifying that an issue is already implemented on the current default branch. Optionally close the issue as completed after a PASS. Use when a user asks whether a branch or merged change completes a GitHub issue, or needs an issue-visible verification comment.
Resolve GitHub PR feedback end-to-end for the branch you are on. Use when you need to fetch all comments on the branch PR, evaluate whether each comment still applies, decide whether it should be addressed, implement fixes, run compile/tests with retry-on-failure, then commit and push the result.
Create Jira issues such as tasks, stories, bugs, or subtasks from user intent. Use when a user asks to open, file, draft, or create a Jira ticket and needs fields validated, issue text composed, Jira API or connector calls made, and the created issue link returned.