컬렉션
컬렉션 copilot

GitHub Copilot 컴패니언 스킬 & 개발 도구 | AI Agent Skills

Claude Code, Cursor, Windsurf용 github copilot companion dev AI Agent Skills 모음입니다. 개발자 워크플로 자동화에 초점을 둡니다.

이 컬렉션은 Copilot을 단일 AI 기능이 아닌 개발 워크플로우 시스템의 일부로 다룹니다. 리뷰 게이트, 문서 업데이트, 테스트 지원, 운영 자동화를 위한 컴패니언 스킬과 툴링을 제공합니다. 일부 도구는 MCP 연결을 지원하지만, 핵심 가치는 실무 품질 향상과 반복 작업 감소입니다.

Primary Install Bridge

Pick One Skill, Then Take the Install Path

This collection should not trap users in comparison mode or pretend to install the whole collection. Its job is to narrow the shortlist to one skill, then send the next click into installation, validation, and rollout. Installation happens on the skill path.

Step 1 / Primary Path

Step 1: Open the installation docs

Move from GitHub Copilot workflow discovery into the install flow, validation checklist, and first command path before comparing anything else.

Open the Install Path
Best-Fit Next Paths

The Next Click Should Keep Narrowing, Not Reset Back To A Generic Directory

Once the install path is clear, move into the solution, CLI, or editorial surface that best matches this collection. That keeps platform, framework, and operations demand narrowing into a more verifiable high-intent journey.

P1 solution

Agent Workflows Solution

A scenario page for users who already know the workflow problem they need to solve.

High-intent solution pages are safer recovery surfaces than broad skill detail expansion.
P2 comparison

Claude Code vs Cursor vs Windsurf

Comparison pages are one of the best ways to prove independent judgment and avoid the mirror-site posture.

Comparisons make Killer-Skills look editorial-first instead of repo-wrapper-first.
Editorial Proof & Trust Signals

Why This Collection Deserves Priority Attention

Reviewed on 2026-04-17 against Copilot workflow fit, installation clarity, operator handoff, and day-to-day delivery usefulness. This page is now positioned as an install-first Copilot companion hub instead of a vague companion-tools list.

We prioritize this page because Copilot users often need review, documentation, testing, and workflow guardrails around the assistant before broader rollout.

Trust Signals

  • - Entries are chosen for practical Copilot workflow value such as review gates, documentation support, testing, and delivery guardrails.
  • - Selection favors tools with public docs and clear setup paths that teams can validate before wider rollout.
  • - The page is curated for repeatable engineering quality, not vague companion-brand adjacency.

Grouping Logic

  • - Lead with tools that can enter a Copilot-centered workflow without adding heavy setup ambiguity.
  • - Keep the shortlist compact enough for quick comparison while still covering review, docs, testing, and automation support.
  • - Use installation as the bridge from Copilot discovery into validated daily execution.

Maintenance & Review

Last Reviewed
2026-04-17
Cadence
Re-check when install flow, maintainer posture, or Copilot workflow relevance changes upstream; otherwise review monthly.
Maintained By
Killer-Skills editorial review within the recovery-focused authority queue.
Verification
Validate installability, operator clarity, workflow fit, and maintainer trust before retaining or adding an entry.
Execution Examples

How These Skills Work Together In Practice

Close the gaps around Copilot first

Use this page when you need one Copilot-adjacent tool that can improve quality and delivery without turning evaluation into another endless tooling loop.

  1. 1. Open the installation docs before opening more Copilot-related repositories.
  2. 2. Choose one tool that best supports review, docs, testing, or automation.
  3. 3. Install it and verify the CLI write path, sync behavior, and first operator checkpoint.
  4. 4. Only after the base path works, expand the setup across the wider team workflow.

Standardize support around Copilot

Treat the collection as an editorial filter when you need Copilot-adjacent tools that improve team quality without overcomplicating the stack.

  1. 1. Check whether the tool has stable ownership and visible install guidance.
  2. 2. Review CLI behavior so operators know what will be written and synced.
  3. 3. Use one validated path before scaling it to more projects or more teammates.
  4. 4. Document the chosen Copilot workflow baseline after the first clean rollout.
After Installation

Supporting Moves After The Install Path Is Clear

Step 2

Step 2: Check CLI write and sync behavior

Confirm what the CLI writes, how sync behaves, and what operators should validate after the install path is clear.
Step 3

Step 3: Cross-check with trusted tools

Use the official trusted collection to sanity-check tool choices before you standardize a team stack.

testing-with-api-mocks

Logo of stacklok
stacklok

Start here for all API mocking in tests. Covers auto-generation, fixtures, and when to use other skills. Required reading before creating, refactoring, or modifying any test involving API calls.

★ 116
⑂ 0
인공지능

testing-api-overrides

Logo of stacklok
stacklok

Test that components send correct query parameters or request arguments. Use when testing filtering, sorting, pagination, or any read operation where request parameters matter. Use for test-scoped mock customization.

★ 0
⑂ 0
개발자

sync-readme

Logo of lbb00
lbb00

sync-readme는 README.md와 README_ZH.md 문서를 동기화하는 도구입니다

★ 17
⑂ 0
인공지능

update-docs

Logo of lbb00
lbb00

Update all project documentation after code changes.

★ 17
⑂ 0
인공지능

memory-updater

Logo of u9401066
u9401066

🔬 AI-powered medical paper writing toolkit — from PubMed search to Word export, all inside VS Code

★ 5
⑂ 0
인공지능

roadmap-updater

Logo of u9401066
u9401066

更新 ROADMAP.md 狀態。觸發：roadmap、路線、規劃、里程碑。

★ 0
⑂ 0
개발자

review-design

Logo of janekbaraniewski
janekbaraniewski

Review a design doc against the codebase

★ 8
⑂ 0
인공지능
Related Authority Collections

If This Page Is Close, Keep Narrowing With Adjacent Authority Pages

Do not reset back to the generic directory. Move sideways through these adjacent high-intent collections to narrow the shortlist toward the install path that best matches your team.

P0 collection

Official AI Skills & Trusted Tools

A high-trust collection that lets the site lead with official and strongly verified ecosystems instead of random long-tail repos.

Trusted-brand collections are the fastest way to rebuild authority after pruning.
P0 collection

Agent Workflow Building Tools

A workflow-first collection that explains why related skills belong together and what job they solve.

Workflow collections add first-party judgment that generic skill detail pages struggle to communicate.
P1 collection

Top Claude Code Skills

A platform-specific collection for one of the clearest demand clusters in the product ecosystem.

Platform collections let the site recover with narrower, more trustworthy topical intent.
P1 collection

Cursor-Compatible Skills

A clean surface for editor-specific demand with explicit workflow intent.

Editor-specific demand should land on curated surfaces, not random repo coverage.
Installation Questions

Answer These Three Questions Before You Install

This collection should not keep users browsing forever. These three questions explain how to shortlist, install, and validate the next step.

이 컬렉션들은 어떤 워크플로를 위해 만들어졌나요?

워크플로 자동화, 프로세스 자동화, 문서 작업, 데이터 워크플로 및 재사용 가능한 스킬 스택을 중심으로 구성되어 있습니다.

컬렉션과 메인 스킬 디렉터리의 차이점은?

스킬 디렉터리는 직접 검색과 필터링에 적합하고, 컬렉션은 완전한 워크플로를 위한 보완적 스킬 묶음을 찾는 데 적합합니다.

이 컬렉션들을 Claude Code나 Cursor에 설치할 수 있나요?

네. 이 컬렉션의 스킬들은 일반적으로 Claude Code, Cursor, Windsurf 및 기타 지원 환경에서 통합 설치 흐름으로 작동합니다.

Additional Recovery Paths

Use These Additional Paths If You Need One More Step To Narrow The Decision

These are the supporting surfaces for this collection after the install direction is clear and the primary next paths have already narrowed the decision.

P1 solution

Workflow Automation Solution

A use-case page for users searching for repeatable automation patterns instead of one-off tools.

Workflow automation demand is easier to satisfy with curated intent clusters than with flat directory coverage.
P0 collection

Agent Workflow Building Tools

A workflow-first collection that explains why related skills belong together and what job they solve.

Workflow collections add first-party judgment that generic skill detail pages struggle to communicate.
Choose One Skill Open Install Guide →