New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Pull Request Workflow

by fossasia in fossasia/eventyay

Branching, commits, PR preparation, and review follow-up for Eventyay contributions

Apache-2.0Auto-check passedDevelopment

Install Pull Request Workflow

skills CLI
$ npx skills add fossasia/eventyay --skill pull-request-workflow -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install fossasia/eventyay pull-request-workflow --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/fossasia/eventyay.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/pull-request-workflow .claude/skills/pull-request-workflow && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
pull-request-workflow
GitHub stars
1.7k
Token cost
~255 tokens
SKILL.md length
118 words
Files
4 (incl. references, assets)
Skills in repo
21
Repo updated
First seen
Licence
Apache-2.0

At a glance

Branching, commits, PR preparation, and review follow-up for Eventyay contributions

  • Works in 6 steps: Create a focused feature branch from dev. → Keep changes scoped to one concern and… → Run targeted checks before requesting… → …
  • Tasks that involve Pull requests
  • SKILL.md covers When to Use, Core Workflow, Guardrails and Supporting Artifacts
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Pull Request Workflow is an agent skill from fossasia/eventyay. Branching, commits, PR preparation, and review follow-up for Eventyay contributions

Its SKILL.md is about 260 tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files, including reference files and assets (for example `assets/pr-description-template.md`, `references/pr-readiness-guide.md` and `tests/review-response-scenarios.md`).

It sits in Development, covering Pull requests. The repository describes itself as: Open Source Event Management, Ticketing and Checkins, Talks and Schedules, Video and Interpretations, Badges, Exhibitions and more https://eventyay.com. The licence is Apache-2.0.

When your agent uses it

  • Tasks that involve Pull requests

Example prompts

  • “/pull-request-workflow”

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Create a focused feature branch from dev.
  2. Keep changes scoped to one concern and update tests for behavior changes.
  3. Run targeted checks before requesting review.
  4. Write a concise commit message that states what changed.
  5. Prepare a clear PR description with context, test evidence, and risk notes.
  6. Address reviewer comments with concrete follow-up commits.

What it can do on your machine

Read from SKILL.md and the folder at commit d4ea632. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Pull Request Workflow loads about 255 tokens when it runs, and up to ~412 if it reads all its reference files. Until then it costs about 26 tokens; SKILL.md has 118 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~26
When it runs · the whole SKILL.md, loaded when a task matches
~255
With references · SKILL.md plus every file in references/, read only if the agent opens them
~412

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from fossasia/eventyay at commit d4ea632, republished under its Apache-2.0 licence (© fossasia). 118 words, ~255 tokens.

Download SKILL.mdSave it as .claude/skills/pull-request-workflow/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.
name
pull-request-workflow
description
Branching, commits, PR preparation, and review follow-up for Eventyay contributions

Skill: Pull Request Workflow

When to Use

Use this skill when preparing changes for review, responding to feedback, and finalizing a PR against dev.

Core Workflow

  1. Create a focused feature branch from dev.
  2. Keep changes scoped to one concern and update tests for behavior changes.
  3. Run targeted checks before requesting review.
  4. Write a concise commit message that states what changed.
  5. Prepare a clear PR description with context, test evidence, and risk notes.
  6. Address reviewer comments with concrete follow-up commits.

Guardrails

  • Follow .github/instructions/git-commit.instructions.md for commit quality.
  • Keep diffs small and avoid unrelated refactors.
  • Do not amend shared history unless explicitly requested.

Supporting Artifacts

  • Workflow playbooks: references/
  • Reusable templates: assets/
  • Example review scenarios: tests/

© fossasia, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 3 other files (references, assets) in .agents/skills/pull-request-workflow of fossasia/eventyay.

  • SKILL.md
  • assets/pr-description-template.md
  • references/pr-readiness-guide.md
  • tests/review-response-scenarios.md

Open the folder on GitHubat commit d4ea632

Compare with similar skills

Pull Request Workflow next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Pull Request Workflow compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Pull Request Workflow this skillfossasia/eventyay1.7k—~255Automated safety check: PassApache-2.0
Finishing a Development Branchobra/superpowers296k5 repos~1.9kAutomated safety check: PassMIT
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Check PRonyx-dot-app/onyx32k2 repos~2.3kAutomated safety check: PassMIT
Understand Diff AnalysisEgonex-AI/Understand-Anything86k1 repos~1.4kAutomated safety check: PassMIT
PR Design DocOpenHands/OpenHands90k—~2.4kAutomated safety check: PassMIT

Similar skills

  • Finishing a Development Branch

    obra/superpowers

    Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.

    296k GitHub starsUsed in 5 repos~1.9k tokens
    DevelopmentAuto-check passed

  • PR Babysitter

    openinterpreter/openinterpreter

    Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.

    69k GitHub starsUsed in 3 repos~4.2k tokens
    DevelopmentAuto-check passed

  • Check PR

    onyx-dot-app/onyx

    Checks a GitHub, GitLab, or Perforce (p4) pull request (or merge request, or shelved changelist) for unresolved review comments, failing status checks, and incomplete PR descriptions.

    32k GitHub starsUsed in 2 repos~2.3k tokens
    DevelopmentAuto-check passed

  • Understand Diff Analysis

    Egonex-AI/Understand-Anything

    Reads your git changes or a pull request against a prebuilt knowledge graph of the project to explain what changed, which components are affected and what is risky.

    86k GitHub starsUsed in 1 repo~1.4k tokens
    DevelopmentAuto-check passed

  • PR Design Doc

    OpenHands/OpenHands

    For a non-trivial pull request, write a self-contained HTML design doc under the temporary .pr/ directory and link a visibility-appropriate preview in the PR description, so maintainers grasp the…

    90k GitHub stars~2.4k tokensUpdated today
    DevelopmentAuto-check passed

  • WooCommerce Code Review

    woocommerce/woocommerce

    Reviews WooCommerce code changes against the project's standards, flagging backend PHP architecture, naming, documentation, data integrity and testing violations.

    11k GitHub starsUsed in 3 repos~1.1k tokens
    DevelopmentAuto-check passed

More from fossasia/eventyay

All 21 skills in this repo

  • Stripe Projects

    fossasia/eventyay

    A skill your agent uses when the user wants to provision infrastructure or third-party services using Stripe Projects.

    1.7k GitHub starsUsed in 5 repos~2k tokens
    Auto-check: notes

  • Stripe Apps

    fossasia/eventyay

    A skill your agent uses when building, modifying, or reviewing a Stripe App — or when the user describes something that implies one (e.g.

    1.7k GitHub starsUsed in 2 repos~3.6k tokens
    Auto-check passed

  • Connect Recommend

    fossasia/eventyay

    A skill your agent uses when the user asks about Stripe Connect configuration, charge patterns, Dashboard access, or how to get started with Connect, is building a marketplace, platform…

    1.7k GitHub starsUsed in 1 repo~5.9k tokens
    Auto-check: warnings

  • Django Run Locally

    fossasia/eventyay

    Steps for initiating the Django development server without Docker

    1.7k GitHub stars~411 tokensUpdated today
    Auto-check passed

  • Docker Deployment

    fossasia/eventyay

    Docker Compose, container services, deployment. An agent skill from fossasia/eventyay.

    1.7k GitHub stars~574 tokensUpdated today
    Auto-check: notes

  • Stripe Best Practices

    fossasia/eventyay

    Guides Stripe integration decisions across development and test environment planning (separate sandboxes vs the shared test mode sandbox), API selection (Checkout Sessions vs PaymentIntents)…

    1.7k GitHub starsUsed in 1 repo~1.7k tokens
    Auto-check passed

Categories

Questions about Pull Request Workflow

What does Pull Request Workflow do?

Branching, commits, PR preparation, and review follow-up for Eventyay contributions. Pull Request Workflow is an agent skill from fossasia/eventyay.

When should I use Pull Request Workflow?

Pull Request Workflow fits situations like: tasks that involve Pull requests.

How do I install Pull Request Workflow in Claude Code?

Run `npx skills add fossasia/eventyay --skill pull-request-workflow -a claude-code`. Or copy the skill folder (.agents/skills/pull-request-workflow in fossasia/eventyay) into .claude/skills/pull-request-workflow in your project. Claude Code loads it when a task matches its description.

How do I install Pull Request Workflow in Codex?

Run `npx skills add fossasia/eventyay --skill pull-request-workflow -a codex`. Or copy the skill folder (.agents/skills/pull-request-workflow in fossasia/eventyay) into .agents/skills/pull-request-workflow in your project. Codex loads it when a task matches its description.

Can I use Pull Request Workflow in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add fossasia/eventyay --skill pull-request-workflow -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/pull-request-workflow, .gemini/skills/pull-request-workflow, .github/skills/pull-request-workflow and .opencode/skills/pull-request-workflow in your project.

What does Pull Request Workflow need to run?

SKILL.md names no scripts, command-line tools or credentials: Pull Request Workflow is instructions for the agent only.

Does Pull Request Workflow access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Pull Request Workflow safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Pull Request Workflow use?

Pull Request Workflow is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Pull Request Workflow use?

About 255 tokens (SKILL.md is roughly 1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 157 tokens, read only when the agent opens those files.

What are the alternatives to Pull Request Workflow?

Skills that share tags, products or a category with Pull Request Workflow: Finishing a Development Branch (obra/superpowers, 296k stars), PR Babysitter (openinterpreter/openinterpreter, 69k stars), Check PR (onyx-dot-app/onyx, 32k stars) and Understand Diff Analysis (Egonex-AI/Understand-Anything, 86k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Pull Request Workflow?

fossasia (a GitHub organization) maintains it in fossasia/eventyay, which has 1,700 GitHub stars. The repository holds 21 skills in this directory. The repository was last updated on October 7, 2026.

Source: fossasia/eventyay on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.