Menü
Experts in asynchronous Git/GitHub collaborative development flow.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
Complete guide to multi-agent collaboration card management, including starting collaborations, joining teams, and creating custom collaboration cards
Complete guide to the OpenSquad multi-agent collaboration system with user authorization gates. Use this skill when starting a collaboration session, coordinating multiple agents, managing the collaboration board, or when you need to understand how to use board_update, board_list, and other collaboration tools. Triggers on "start collaboration", "assign tasks", "update progress", "write report", or when working with other agents in a group chat.
Create an Agent that can send/receive messages and hold normal conversations in a specified group. Covers the full flow: register IM account → create Agent directory → assign a model card → write role.md → configure config.json (note: tools must include "im") → join the group → start.
Connect OpenSquad agents to external IM platforms (Feishu/Lark, QQ, Telegram). Covers plugin service setup, adapter processes, Gateway auth, workspace path fixes, and troubleshooting. Uses Feishu as the reference example.
Allows the agent to self-configure and deploy MCP servers. Covers central config, per-agent sync, web UI visibility, registration diagnostics, and validation.
Complete guide for publishing a local skill to the public OpenSquad skill library, including lessons learned on BOM handling, path issues, and other gotchas.
| name | vcs_collaboration |
| description | Experts in asynchronous Git/GitHub collaborative development flow. |
| allowed-tools | git, vcs, filesystem, im |
This skill enables agents to participate in complex, multi-agent software development using Git and GitHub within the OpenSquad local-first architecture. It emphasizes Local Branching Isolation and VCS Audit Transparency.
In OpenSquad, agents share the same physical directory. To avoid collision:
git.checkout(target="agent_id/feat-name", create=True).main or dev unless you are the PM or Reviewer during a merge.git commit --no-verify or other commands that bypass hooks.git.checkout(target="agent_id/feat-name", create=True).git_core plugin will automatically inject your Agent ID as the author.git.checkout(target="main") -> git.pull() -> git.checkout(target="your-branch") -> git.rebase(upstream="main").Only agents designated as "VCS Coordinator" (holding the master GitHub token) should perform remote operations:
git.push(remote="origin", branch="main").vcs.pr_create(repo="owner/repo", title="...", body="...").For practical messaging patterns and handoff scenarios, refer to HANDOFF_EXAMPLES.md. Always follow the "@mention + [STATUS/BUG/PHASE]" message format to maintain team visibility.
When you receive a notification (via Group Chat or Event) that a PR has been commented on or created:
git.fetch -> git.checkout.filesystem.read_file.vcs.issue_comment(issue_id, body="..."). Focus on logic, security, and style.vcs.issue_view.If git.rebase fails:
git.diff to identify the conflict markers (<<<<<<<, =======, >>>>>>>).git.add followed by git.commit.@agent_name in group chat for urgent PR reviews.