home / skills / baz-scm / awesome-reviewers / team-collaboration

team-collaboration skill

/_skills/team-collaboration

This skill helps you collaborate effectively on code reviews and open-source contributions by promoting clear communication and adherence to project guidelines.

npx playbooks add skill baz-scm/awesome-reviewers --skill team-collaboration

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
2.0 KB
---
name: team-collaboration
description: Working effectively with others in coding projects – including code reviews, clear communication, and contributing to shared or open-source codebases.
version: '1.0'
---
# Collaboration & Open Source Contribution

Building software is usually a team effort. Strong collaboration skills – communicating with team members, reviewing each other’s code, and following shared conventions – are essential. Many developers also participate in open-source projects to share knowledge and improve their skills. Contributing to open source is recommended for new developers to gain experience and visibility. Ultimately, being able to work well with others (often asynchronously, across different time zones or via platforms like GitHub) is a key developer superpower.

## Examples
- Participating in code review: reviewing a colleague’s pull request and providing constructive feedback, as well as responding to feedback on your own code.
- Contributing a bug fix or new feature to an open-source project, following the project’s contribution guidelines and coding style.

## Guidelines
- **Code Review Mastery:** Engage in code reviews regularly. Read others’ code and provide helpful suggestions, and incorporate feedback from reviewers on your code. For example, if reviewers suggest a function be split for clarity, be willing to refactor. Code review culture leads to better code quality and knowledge transfer.
- **Open Source Engagement:** Consider contributing to open-source projects or internal company repositories. This exposes you to large-scale codebases and different perspectives. It’s also a great way to demonstrate skills. Always follow the project’s contribution guidelines when submitting changes.
- **Team Communication:** Maintain clear and professional communication with team members. Document decisions, update project artifacts, and respect established team conventions. By aligning with team processes, you build trust and velocity in development.

Overview

This skill helps developers work effectively with others in coding projects by focusing on code reviews, clear team communication, and contributing to shared or open-source codebases. It provides ready-to-use prompts and practices to improve review quality, streamline contributions, and align with team conventions. Use it to build collaborative habits that raise code quality and project velocity.

How this skill works

The skill supplies system prompts and guidance for agentic code review workflows and collaboration tasks. It inspects pull request content, suggests actionable review comments, and recommends follow-up changes based on project guidelines. It also offers templates for contribution PRs, issue engagement, and clear team communication to ensure consistent interactions.

When to use it

  • Reviewing a teammate’s pull request and composing constructive feedback.
  • Preparing a contribution to an open-source project or internal repo.
  • Responding to review feedback and planning follow-up changes.
  • Onboarding to a new team to learn coding conventions and processes.
  • Coordinating work across distributed teams or asynchronous workflows.

Best practices

  • Give actionable, bite-sized review comments focused on behavior and rationale.
  • Follow the project’s contribution guidelines and coding style before submitting PRs.
  • Document design decisions and link related issues or specs in PR descriptions.
  • Be respectful and solution-oriented in feedback; suggest concrete fixes when possible.
  • Iterate on feedback promptly and close the loop by summarizing changes.

Example use cases

  • Run an agentic review to generate a checklist of issues for a large pull request.
  • Use templates to craft a clear PR description that speeds reviewer onboarding.
  • Apply review prompts to convert high-level feedback into specific code edits.
  • Prepare a first-time contribution to an open-source project with step-by-step guidance.
  • Coordinate cross-team changes by producing a concise summary of impact and migration steps.

FAQ

How do I keep reviews constructive and not personal?

Focus on code behavior and outcomes, explain why a change helps, and offer concrete suggestions rather than judgments.

What should a good PR description include?

Purpose of the change, related issue links, high-level approach, testing steps, and any migration or rollout notes.