본문으로 건너뛰기
cccskills
무료GitHub에 공개

github-copilot-agent-tips-and-tricks

Find and review pull requests created with GitHub Copilot using author searches, branch names, and Git history. Follow practical checks for changes and tests, and export request lists to CSV to track contributions.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

원문원문 설명 보기

Practical tips for reviewing and improving Copilot agent PRs.

연동 도구GitHub
설치 방법 보기

이럴 때 유용합니다

  • Finding pull requests created by Copilot
  • Checking changes, commit history, and tests before merging
  • Exporting Copilot contribution lists to CSV
  • Troubleshooting searches that return no results

포함된 파일(1)

  • SKILL.md6.3 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

GitHub Copilot Agent Tips and Tricks

Use this guide to find, review, and work with Copilot coding agent pull requests in gh-aw.

Identifying Copilot Agent PRs

Branch Naming Convention

Copilot coding agent branches use the copilot/ prefix, which makes them easy to identify and filter.

Examples from this repository:

  • copilot/add-cache-for-imported-workflows
  • copilot/fix-istruthy-bundling-issue
  • copilot/update-audit-command-copilot
  • copilot/refactor-mcp-tool-rendering

Author Attribution

Copilot coding agent PRs are typically authored by:

  • app/github-copilot - The GitHub Copilot bot account
  • Individual developers using Copilot as an assistant

Searching for Copilot Agent PRs

Using GitHub CLI (gh)

Prerequisites:

# Authenticate with GitHub CLI
gh auth login

Search by author (GitHub Copilot bot):

# List all PRs created by the Copilot bot
gh pr list --author "app/github-copilot" --limit 100

# Include closed PRs
gh pr list --author "app/github-copilot" --state all --limit 100

# Get detailed JSON output
gh pr list --author "app/github-copilot" --json number,title,author,headRefName,createdAt,state

Search by branch prefix:

# Find all PRs from copilot/* branches
gh pr list --search "head:copilot/" --state all

# Combine with other filters
gh pr list --search "head:copilot/ is:open"
gh pr list --search "head:copilot/ is:merged"

Filter with jq:

# Extract specific fields
gh pr list --limit 100 --json author,number,title,headRefName \
  --jq '.[] | select(.headRefName | startswith("copilot/")) | {number, title, branch: .headRefName}'

# Filter by author containing "copilot"
gh pr list --limit 100 --json author,number,title \
  --jq '.[] | select(.author.login | contains("copilot"))'

Using Git Commands

List copilot branches:

# Local and remote copilot branches
git branch -a | grep copilot

# Remote copilot branches only
git branch -r | grep copilot

Search commit history:

# Find commits with "copilot" in message
git log --all --grep="copilot" --oneline

# Find commits by copilot author
git log --all --author="copilot" --oneline

# Show graph with copilot-related commits
git log --all --grep="copilot" --oneline --graph

Find merged copilot PRs:

# Search for merge commits
git log --all --merges --grep="copilot" --oneline

# With PR numbers
git log --all --merges --oneline | grep -i copilot

Common Copilot Agent PR Patterns

Recent Examples from gh-aw Repository

Based on analysis of this repository, Copilot coding agent PRs typically address:

  1. Refactoring and Code Organization

    • Example: "Refactor ALL_TOOLS to separate JSON file with runtime filtering"
    • Example: "Eliminate duplicate MCP tool table rendering logic"
  2. Documentation Improvements

    • Example: "Document strict mode enforcement areas and CLI flag in schema"
    • Example: "Add comprehensive strict mode reference documentation"
  3. Bug Fixes

    • Example: "Fix JavaScript test assertions for loadAgentOutput error handling"
    • Example: "Remove duplicate formatFileSize() function"
  4. Testing Enhancements

    • Example: "Add integration tests for playwright MCP configuration across all engines"
  5. Security Fixes

    • Example: "Fix template injection risk in copilot-session-insights workflow"

PR Metadata to Check

When reviewing Copilot coding agent PRs, pay attention to:

  • Branch name: Should follow copilot/descriptive-name pattern
  • Commit messages: Often include "Initial plan" commits
  • PR description: Should explain the problem and solution
  • Linked issues: May reference issues being addressed

Workflow Tips

Finding Related PRs

# Find PRs related to a specific feature
gh pr list --search "head:copilot/ refactor" --state all

# Find PRs in a date range
gh pr list --search "head:copilot/ created:>=2024-01-01" --state all

# Find PRs with specific labels
gh pr list --search "head:copilot/ label:enhancement"

Reviewing Copilot PRs

# Check out a copilot PR locally
gh pr checkout <PR-number>

# View PR diff
gh pr diff <PR-number>

# View PR details
gh pr view <PR-number>

# View PR in browser
gh pr view <PR-number> --web

Tracking Copilot Contributions

# Count merged copilot PRs
gh pr list --author "app/github-copilot" --state merged --json number --jq 'length'

# List recent copilot PRs with dates
gh pr list --author "app/github-copilot" --state all --limit 20 \
  --json number,title,createdAt,state \
  --jq '.[] | "\(.number): \(.title) (\(.state)) - \(.createdAt)"'

# Export to CSV for analysis
gh pr list --author "app/github-copilot" --state all --limit 100 \
  --json number,title,createdAt,state,author \
  --jq -r '.[] | [.number, .title, .state, .createdAt] | @csv' > copilot-prs.csv

Troubleshooting

Authentication Issues

If you see "gh auth login" prompts:

# Authenticate with GitHub CLI
gh auth login

# Or set token environment variable
export GH_TOKEN="your-github-token"

No Results Found

If searches return no results:

  1. Verify you're in the correct repository
  2. Check if the author name is correct (try app/github-copilot or github-copilot)
  3. Try searching by branch prefix instead: gh pr list --search "head:copilot/"
  4. Check if PRs exist: git branch -r | grep copilot

Rate Limiting

If you hit GitHub API rate limits:

# Check rate limit status
gh api rate_limit

# Use authenticated requests (higher limits)
gh auth login

Best Practices

  1. Use branch prefix search when author search is unavailable
  2. Export PR lists regularly for tracking and analysis
  3. Review commit history to understand Copilot's implementation approach
  4. Check for "Initial plan" commits to see Copilot's planning process
  5. Verify tests pass before merging Copilot PRs
  6. Review security implications especially for workflow changes

Additional Resources

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

Coordinate work across AI agents with shared rules for locating team files, recording decisions and their reasons, and requesting help. It also defines who owns revisions after a reviewer rejects an artifact.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Locate team files across separate working directories
  • Record decisions that affect other agents
  • Request input from another specialist
github/gh-aw5.4천2026년 10월 20일 업데이트

Set shared development rules for an agent team: keep specific agent names out of product code, tests, and CI configuration, verify affected tests before finishing, and record lessons learned from mistakes.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Share development rules across multiple agents
  • Keep team-specific agent names out of code and tests
  • Check affected tests before declaring work complete
github/gh-aw5.4천2026년 10월 20일 업데이트

Routes requests to design, create, update, debug, or upgrade GitHub Agentic Workflows to the appropriate instructions. It helps the agent select a workflow-specific procedure and apply any additional rules defined for the repository.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Designing a new workflow through questions
  • Investigating failed runs and recurring errors
  • Upgrading workflows and addressing deprecations
github/gh-aw5.4천2026년 10월 20일 업데이트

Prepare architecture proposals before implementation so the team can agree on a direction. Organize evidence, technical choices, effects on existing work, risks, and the first release’s scope into a document with clear recommendations and decision owners.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Proposing a major architecture change
  • Replanning milestones after a foundation change
  • Comparing technical options before seeking approval
github/gh-aw5.4천2026년 10월 20일 업데이트

Update the gh-aw-firewall version used by gh-aw, rebuild generated files, and review release notes and configuration schemas, which define valid settings. It guides related code and test updates while identifying follow-up work that remains.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Updating the firewall version used by gh-aw
  • Reviewing release notes for integration changes
  • Checking configuration schema differences
github/gh-aw5.4천2026년 10월 20일 업데이트

Review git and gh operations in gh-aw workflows to check credential availability for each repository. Identify missing token handoffs, risky expansions of limited checkouts, and error handling needed where credentials are intentionally unavailable.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Reviewing git operations after repository checkout
  • Checking tokens for private cross-repository access
  • Reviewing sparse and shallow checkout changes
github/gh-aw5.4천2026년 10월 20일 업데이트

github의 스킬 모두 보기

이 스킬의 문제 신고