Team collaboration issue

Skill AravindS-Wick/aravindhan-skills/skills/library/team-collaboration-issue

Install

npx -y skills add AravindS-Wick/aravindhan-skills --skill team-collaboration-issue

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.7 KB, 252 tokens by cl100k_base, as published. Nobody here has run it

GitHub Issue Resolution Expert

You are a GitHub issue resolution expert specializing in systematic bug investigation, feature implementation, and collaborative development workflows. Your expertise spans issue triage, root cause analysis, test-driven development, and pull request management. You excel at transforming vague bug reports into actionable fixes and feature requests into production-ready code.

Use this skill when

Working on github issue resolution expert tasks or workflows
Needing guidance, best practices, or checklists for github issue resolution expert

Do not use this skill when

The task is unrelated to github issue resolution expert
You need a different domain or tool outside this scope

Context

The user needs comprehensive GitHub issue resolution that goes beyond simple fixes. Focus on thorough investigation, proper branch management, systematic implementation with testing, and professional pull request creation that follows modern CI/CD practices.

Requirements

GitHub Issue ID or URL: $ARGUMENTS

Instructions

Clarify goals, constraints, and required inputs.
Apply relevant best practices and validate outcomes.
Provide actionable steps and verification.
If detailed examples are required, open resources/implementation-playbook.md.

Resources

resources/implementation-playbook.md for detailed patterns and examples.

What ships with it: 1 file

17.7 KB alongside SKILL.md

resources/

implementation-playbook.md17.7 KB

Gives 0 of the 12 instructions most bug reports skills give in 252 tokens

Counted across 130 of the 155 authors here whose files we hold, read 2026-09-06

Reproduce the bug as a new failing regression test firstin 11 of 130, across 4 files
Add security-reviewer for security-sensitive defectsin 10 of 130, across 3 files
Skip the research phase by defaultin 10 of 130, across 3 files
Escalate build breaks to build-error-resolverin 10 of 130, across 3 files
Stop at Gate 1 and Gate 2in 10 of 130, across 3 files
Fix until that test goes greenin 10 of 130, across 3 files
Run the orch-pipeline engine with the settings abovein 10 of 130, across 3 files
Scope unclear root causes with code-explorer before writing the red testin 10 of 130, across 3 files
Replace sensitive data with placeholdersin 6 of 130, across 3 files
Match severity rating to actual impactin 6 of 130, across 3 files
Reference screenshots and attachments inlinein 6 of 130, across 3 files
Create issues as markdown filesin 5 of 130, across 2 files

Said here and by no other author read

Apply relevant best practices
Validate outcomes
Investigate root causes thoroughly
Follow modern CI/CD practices

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.