aaaaqwq/collaboration
skills/collaboration/SKILL.md
Guide for collaborating on GitHub projects. This skill should be used when contributing to projects, creating PRs, reviewing code, or managing issues on GitHub.
$ install --global
skillsauthnpx skillsauth add aaaaqwq/agi-super-team collaborationInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 29, 2026, 12:15 AM240.1s1 file scanned
SKILL.md
- name:
- collaboration
- description:
- Guide for collaborating on GitHub projects. This skill should be used when contributing to projects, creating PRs, reviewing code, or managing issues on GitHub.
- license:
- MIT
Collaboration
This skill documents how to collaborate on projects on GitHub.
Working on Projects
With write access
If you have write access to the project, you may work directly in the project.
With read-only access
If you only have read-only access and cannot write directly to any branches:
- Create a fork under your own GitHub user account
- Work exclusively on the fork, not the original repository
- The fork is your workspace for all development
Making Changes
To submit changes to a project:
- Create a new branch (never commit directly to main)
- Make commits on this branch as work progresses
- When ready, create a PR from the working branch towards the main branch (from one repo to another if it's a fork)
Code Reviews
When asked to review code:
- Do the review directly on the GitHub PR
- Add comments inline in the code where they make sense
- Use general PR comments only for overarching feedback
Addressing Review Comments
When responding to review feedback:
- Address comments on GitHub, not just in code
- Reply to each comment explaining what was changed or why something was kept
- Mark conversations as resolved when the feedback has been addressed
After PR is Merged
Once a PR has been merged:
- Switch back to the main branch
- Pull from origin to sync with the merged changes
Issues
Always create GitHub issues on the original repository, never on the fork. The fork is only for development work, if needed.
Related Skills
aaaaqwq/code-exemplars-blueprint-generator
development
VerifiedTrustedCommunity
Technology-agnostic prompt generator that creates customizable AI prompts for scanning codebases and identifying high-quality code exemplars. Supports multiple programming languages (.NET, Java, JavaScript, TypeScript, React, Angular, Python) with configurable analysis depth, categorization methods, and documentation formats to establish coding standards and maintain consistency across development teams.
37SKILL.mdUpdated Apr 11, 2026
aaaaqwq/chrome-devtools
tools
VerifiedTrustedCommunity
Expert-level browser automation, debugging, and performance analysis using Chrome DevTools MCP. Use for interacting with web pages, capturing screenshots, analyzing network traffic, and profiling performance.
37SKILL.mdUpdated Apr 11, 2026
aaaaqwq/breakdown-feature-implementation
data-ai
VerifiedTrustedCommunity
Prompt for creating detailed feature implementation plans, following Epoch monorepo structure.
37SKILL.mdUpdated Apr 11, 2026
aaaaqwq/boost-prompt
tools
VerifiedTrustedCommunity
Interactive prompt refinement workflow: interrogates scope, deliverables, constraints; copies final markdown to clipboard; never writes code. Requires the Joyride extension.
37SKILL.mdUpdated Apr 11, 2026