Adoption

Agent Skills are supported by leading AI development tools.

VS Code Gemini CLI GitHub Goose Amp Cursor Claude Code Letta OpenCode Claude OpenAI Codex Factory VS Code Gemini CLI GitHub Goose Amp Cursor Claude Code Letta OpenCode Claude OpenAI Codex Factory

zoeyzou/pr-workflow

Name: pr-workflow
Author: zoeyzou

.cursor/skills/pr-workflow/SKILL.md

npx skillsauth add zoeyzou/friend-sync pr-workflow

Clean

TrivyContainer and dependency vulnerability scanner

Clean

SemgrepStatic code analysis for vulnerabilities

Clean

mcp-scan (Snyk)Model Context Protocol security validation

Skipped

Snyk (dep)Open source security scanning

Skipped

Socket.devSupply chain security analysis

Skipped

VirusTotalMulti-engine malware detection

Skipped

CrowdStrikeAdvanced threat intelligence

Skipped

OSV-ScannerOpen Source Vulnerability database check

Skipped

OWASP Dep-Check

PR Workflow

This skill describes how the agent should help with pull requests in this repo.

When to apply this skill

Use this skill when:

The user asks to create, update, or summarize a PR
The user wants a list of changes grouped into logical commits for review
You need to draft PR titles/descriptions that match the existing style
The user wants a PR checklist before merging

Git & PR conventions

Branches:
- Work happens on feature branches (for example feature/new-design)
- PRs target main unless the user says otherwise
Commits:
- Prefer small, focused commits with imperative subject lines
- Use prefixes like feat:, fix:, chore:, style:, refactor: when appropriate
PR titles:
- Summarize the main user-visible change
- Avoid implementation details in the title

Step-by-step: creating a PR

When the user asks you to open a PR:

Understand the diff
- Run git status and git diff (and git diff --cached if needed)
- Group changes into 1–3 logical bullets (features, refactors, infra)
Check branch state
- Run git rev-parse --abbrev-ref HEAD to confirm you are on the feature branch
- If the branch is behind main, suggest the user rebase or merge before opening the PR
Draft the PR title
- Use the format: <type>: <short description>
- Examples:
  - feat: add FriendTrack dashboard shell
  - fix: handle missing auth secret gracefully

Draft the PR body

Use this template:

## Summary
- [high-level change 1]
- [high-level change 2]

## Details
- [optional: note breaking changes, migrations, env vars]

## Screenshots
- [optional: desktop]
- [optional: mobile]

## Checklist
- [ ] Tests pass locally (`npm test` / `npm run typecheck`)
- [ ] Linting passes (`npm run check`)
- [ ] Migrations applied (`npm run db:full` or equivalent) if schema changed

Create the PR (using gh)
- Use the gh CLI when available:
  - gh pr create --base main --head <current-branch> --title "<title>" --body "<body>"
- If gh is not configured, output the title and body and tell the user to paste them into the GitHub UI.

Updating an existing PR

When the user wants to update an open PR:

Confirm whether new commits are needed or only the description needs refining.
For description changes, re-run the summary/Details/Checklist template and provide an updated body.
Suggest adding screenshots or links to staging if that will help reviewers.

Example interaction

User: "Open a PR for the new dashboard design."

Agent (using this skill):

Inspect commits on the feature branch.
Draft:
- Title: feat: add FriendTrack dashboard shell and routed pages
- Body using the template above, listing overview/friends/meetups/reminders pages and auth changes.
Run gh pr create or output the ready-to-paste text.

zoeyzou/pr-workflow

.cursor/skills/pr-workflow/SKILL.md

Guides the agent through creating, updating, and summarizing pull requests using this repository's git and GitHub conventions. Use when the user wants to open a PR, refine its description, or understand what will be included.

documentation

Updated Apr 17, 2026

$ install --global

skillsauth

npx skillsauth add zoeyzou/friend-sync pr-workflow

Install 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.

Scanners Passed

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 17, 2026, 10:29 AM9.4s1 file scanned

SKILL.md

name:: pr-workflow
description:: Guides the agent through creating, updating, and summarizing pull requests using this repository's git and GitHub conventions. Use when the user wants to open a PR, refine its description, or understand what will be included.

PR Workflow

This skill describes how the agent should help with pull requests in this repo.

When to apply this skill

Use this skill when:

The user asks to create, update, or summarize a PR
The user wants a list of changes grouped into logical commits for review
You need to draft PR titles/descriptions that match the existing style
The user wants a PR checklist before merging

Git & PR conventions

Branches:
- Work happens on feature branches (for example feature/new-design)
- PRs target main unless the user says otherwise
Commits:
- Prefer small, focused commits with imperative subject lines
- Use prefixes like feat:, fix:, chore:, style:, refactor: when appropriate
PR titles:
- Summarize the main user-visible change
- Avoid implementation details in the title

Step-by-step: creating a PR

When the user asks you to open a PR:

Understand the diff
- Run git status and git diff (and git diff --cached if needed)
- Group changes into 1–3 logical bullets (features, refactors, infra)
Check branch state
- Run git rev-parse --abbrev-ref HEAD to confirm you are on the feature branch
- If the branch is behind main, suggest the user rebase or merge before opening the PR
Draft the PR title
- Use the format: <type>: <short description>
- Examples:
  - feat: add FriendTrack dashboard shell
  - fix: handle missing auth secret gracefully

Draft the PR body

Use this template:

## Summary
- [high-level change 1]
- [high-level change 2]

## Details
- [optional: note breaking changes, migrations, env vars]

## Screenshots
- [optional: desktop]
- [optional: mobile]

## Checklist
- [ ] Tests pass locally (`npm test` / `npm run typecheck`)
- [ ] Linting passes (`npm run check`)
- [ ] Migrations applied (`npm run db:full` or equivalent) if schema changed

Create the PR (using gh)
- Use the gh CLI when available:
  - gh pr create --base main --head <current-branch> --title "<title>" --body "<body>"
- If gh is not configured, output the title and body and tell the user to paste them into the GitHub UI.

Updating an existing PR

When the user wants to update an open PR:

Confirm whether new commits are needed or only the description needs refining.
For description changes, re-run the summary/Details/Checklist template and provide an updated body.
Suggest adding screenshots or links to staging if that will help reviewers.

Example interaction

User: "Open a PR for the new dashboard design."

Agent (using this skill):

Inspect commits on the feature branch.
Draft:
- Title: feat: add FriendTrack dashboard shell and routed pages
- Body using the template above, listing overview/friends/meetups/reminders pages and auth changes.
Run gh pr create or output the ready-to-paste text.

Related Skills

zoeyzou/code-review-best-practices

development

VerifiedTrustedCommunity

Reviews changes for security, scalability, performance, code reuse, and maintainability using a structured checklist. Use when the user asks for a code review, wants feedback on a PR, or wants to harden code quality.

SKILL.mdUpdated Apr 17, 2026

zoeyzou/code-review-best-practices

steipete/gh-issues

documentation

VerifiedTrustedCommunity

Fetch GitHub issues, spawn sub-agents to implement fixes and open PRs, then monitor and address PR review comments. Usage: /gh-issues [owner/repo] [--label bug] [--limit 5] [--milestone v1.0] [--assignee @me] [--fork user/repo] [--watch] [--interval 5] [--reviews-only] [--cron] [--dry-run] [--model glm-5] [--notify-channel -1002381931352]

356,423SKILL.mdUpdated Apr 13, 2026

steipete/wiki-maintainer

documentation

VerifiedTrustedCommunity

Maintain the OpenClaw memory wiki vault with deterministic pages, managed blocks, and source-backed updates.

356,423SKILL.mdUpdated Apr 13, 2026

steipete/wiki-maintainer

steipete/feishu-wiki

documentation

VerifiedTrustedCommunity

Feishu knowledge base navigation. Activate when user mentions knowledge base, wiki, or wiki links.

356,423SKILL.mdUpdated Apr 13, 2026

Download

For Claude Desktop. Download once, then upload the file in the app — no terminal needed.

Need help? View full Cowork setup guide →

Install manually

Choose your platform

# Clone the repo
git clone https://github.com/zoeyzou/friend-sync.git

# Copy into Claude Code skills folder (global)
cp -r friend-sync/.cursor/skills/pr-workflow ~/.claude/skills/

Claude Code Skills — official skills path docs.

Repository

zoeyzou/friend-sync

Compatible with

Claude Code

OpenAI Codex CLI

ChatGPT