원클릭으로 Manus에서 모든 스킬 실행

시작하기

vcs-collaboration

스타4

포크2

업데이트2026년 6월 30일 13:39

Experts in asynchronous Git/GitHub collaborative development flow.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

opensquad-ai

opensquad-ai/opensquad

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

VCS Collaboration Skill (OpenSquad Edition)

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.

1. Local Shared Workspace Etiquette

In OpenSquad, agents share the same physical directory. To avoid collision:

ALWAYS check out a new branch for your task: git.checkout(target="agent_id/feat-name", create=True).
NEVER modify files directly on main or dev unless you are the PM or Reviewer during a merge.
NEVER use git commit --no-verify or other commands that bypass hooks.

2. Implementation & Handoff Loop

Assigned: When PM assigns a task via @mention, acknowledge receipt in group chat.
Setup: Switch to a feature branch: git.checkout(target="agent_id/feat-name", create=True).
Commit: Perform atomic commits. The git_core plugin will automatically inject your Agent ID as the author.
Handoff: Once complete, notify the Senior/Reviewer in group chat: "@Senior_Bot, feature logic finished on branch agent_id/feat-name. Please review and merge."
Sync: If someone else merged to main, rebase your branch: git.checkout(target="main") -> git.pull() -> git.checkout(target="your-branch") -> git.rebase(upstream="main").

3. Remote Synchronization (VCS Coordinator Only)

Only agents designated as "VCS Coordinator" (holding the master GitHub token) should perform remote operations:

Push: git.push(remote="origin", branch="main").
PR: vcs.pr_create(repo="owner/repo", title="...", body="...").
Audit: All remote actions are logged in the VCS Audit Timeline. Review this UI periodically to ensure transparency.

4. Communication Examples

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.

3. Asynchronous Code Review

When you receive a notification (via Group Chat or Event) that a PR has been commented on or created:

As a Reviewer:

Fetch the PR branch: git.fetch -> git.checkout.
Analyze the code using filesystem.read_file.
Provide feedback using vcs.issue_comment(issue_id, body="..."). Focus on logic, security, and style.

As a Coder (Fixing Feedback):

Read the comments using vcs.issue_view.
Apply fixes in your local branch.
Commit and Push again. The PR will update automatically.

4. Conflict Resolution

If git.rebase fails:

Use git.diff to identify the conflict markers (<<<<<<<, =======, >>>>>>>).
Read the files and determine the best logical merge.
Edit the file to resolve the markers.
Run git.add followed by git.commit.

5. Collaboration Etiquette

Mentions: Use @agent_name in group chat for urgent PR reviews.
Atomic Commits: Don't mix multiple features in one PR.
Clear PR Descriptions: Link to the Issue using "Closes #123" in the body.

이 저장소의 다른 Skills

같은 저장소

collaboration-management

opensquad-ai/opensquad

Complete guide to multi-agent collaboration card management, including starting collaborations, joining teams, and creating custom collaboration cards

2026-06-294

collaboration-workflow

opensquad-ai/opensquad

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.

2026-06-294

create-agent

opensquad-ai/opensquad

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.

2026-06-294

external-im-integration

opensquad-ai/opensquad

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.

2026-06-294

mcp-auto-deploy

opensquad-ai/opensquad

Allows the agent to self-configure and deploy MCP servers. Covers central config, per-agent sync, web UI visibility, registration diagnostics, and validation.

2026-06-294

publish-skill

opensquad-ai/opensquad

Complete guide for publishing a local skill to the public OpenSquad skill library, including lessons learned on BOM handling, path issues, and other gotchas.

2026-06-294

name	vcs_collaboration
description	Experts in asynchronous Git/GitHub collaborative development flow.
allowed-tools	git, vcs, filesystem, im

VCS Collaboration Skill (OpenSquad Edition)

1. Local Shared Workspace Etiquette

In OpenSquad, agents share the same physical directory. To avoid collision:

ALWAYS check out a new branch for your task: git.checkout(target="agent_id/feat-name", create=True).
NEVER modify files directly on main or dev unless you are the PM or Reviewer during a merge.
NEVER use git commit --no-verify or other commands that bypass hooks.

2. Implementation & Handoff Loop

Assigned: When PM assigns a task via @mention, acknowledge receipt in group chat.
Setup: Switch to a feature branch: git.checkout(target="agent_id/feat-name", create=True).
Commit: Perform atomic commits. The git_core plugin will automatically inject your Agent ID as the author.
Handoff: Once complete, notify the Senior/Reviewer in group chat: "@Senior_Bot, feature logic finished on branch agent_id/feat-name. Please review and merge."
Sync: If someone else merged to main, rebase your branch: git.checkout(target="main") -> git.pull() -> git.checkout(target="your-branch") -> git.rebase(upstream="main").

3. Remote Synchronization (VCS Coordinator Only)

Only agents designated as "VCS Coordinator" (holding the master GitHub token) should perform remote operations:

Push: git.push(remote="origin", branch="main").
PR: vcs.pr_create(repo="owner/repo", title="...", body="...").
Audit: All remote actions are logged in the VCS Audit Timeline. Review this UI periodically to ensure transparency.

4. Communication Examples

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.

3. Asynchronous Code Review

When you receive a notification (via Group Chat or Event) that a PR has been commented on or created:

As a Reviewer:

Fetch the PR branch: git.fetch -> git.checkout.
Analyze the code using filesystem.read_file.
Provide feedback using vcs.issue_comment(issue_id, body="..."). Focus on logic, security, and style.

As a Coder (Fixing Feedback):

Read the comments using vcs.issue_view.
Apply fixes in your local branch.
Commit and Push again. The PR will update automatically.

4. Conflict Resolution

If git.rebase fails:

Use git.diff to identify the conflict markers (<<<<<<<, =======, >>>>>>>).
Read the files and determine the best logical merge.
Edit the file to resolve the markers.
Run git.add followed by git.commit.

5. Collaboration Etiquette

Mentions: Use @agent_name in group chat for urgent PR reviews.
Atomic Commits: Don't mix multiple features in one PR.
Clear PR Descriptions: Link to the Issue using "Closes #123" in the body.