Claude Code Plugins

Community-maintained marketplace

Feedback

PR-and-check

@klaushofrichter/een-oauth-proxy
0
0

Use this skill when you are requested to create a PR for a feature branch.

Install Skill

1Download skill
2Enable skills in Claude

Open claude.ai/settings/capabilities and find the "Skills" section

3Upload to Claude

Click "Upload skill" and select the downloaded ZIP file

Note: Please verify skill by going through its instructions before using it.

SKILL.md

name PR-and-check
description Use this skill when you are requested to create a PR for a feature branch.

Instructions

1. Validate branch

  • Verify we're on a feature branch (not develop or production)
    • check current branch: git branch --show-current
    • if on develop or production, report error and stop

2. Check for existing PR

  • Check if a PR already exists for this branch: gh pr list --head <branch-name> --json number,url
  • If a PR exists, report the existing PR URL and skip to step 5 (code review)

3. Run tests locally

  • Run the proxy API tests first (these don't need a running proxy - they use vitest's mock worker)
    • run: npm test in the proxy directory
    • if tests fail, analyse the failure, report findings, and stop
  • Start the local proxy for integration tests
    • check if proxy is running: lsof -i :8787 | grep LISTEN
    • terminate existing proxy if running: lsof -i :8787 -t | xargs kill
    • start proxy in background: run npm run dev in the proxy directory with run_in_background: true
    • wait a few seconds for the proxy to start, then verify it's running
  • Run the remaining test suites sequentially - these can not run in parallel as the apps use the same port 3333
    • run the admin tests: npm test in the admin directory
    • run the demo1 tests: npx playwright test in the demo1 directory
    • if any test fails, analyse the failure, report findings, and stop
  • Cleanup: terminate the local proxy after tests complete
    • lsof -i :8787 -t | xargs kill

4. Create PR

  • Get version numbers for the PR body:
    • jq -r .version proxy/package.json (and similarly for admin, demo1)
  • Create a well-formatted PR from the feature branch to develop:
    • use gh pr create --base develop --title "<title>" --body "<body>" with a HEREDOC for the body
    • highlight the changes and the purpose of the feature branch
    • include test results summary and version numbers
  • Capture the PR number from the output (needed for code review step)
    • the gh pr create command outputs the PR URL, extract the number from it

5. monitor code review

  • A code review using the workflow pr-review.yml was automatically triggered by the PR
  • Verify the workflow started:
    • wait 5 seconds, then check: gh run list --workflow=pr-review.yml --limit 1 --json databaseId,status,headBranch
    • confirm the run is for the correct branch
    • if workflow failed to start, report error and stop
  • Poll for completion (check once per minute, max 10 minutes total):
    • gh run list --workflow=pr-review.yml --limit 1 --json databaseId,status,conclusion
  • Check the result:
    • if the workflow did not finish within 10 minutes, report timeout and stop
    • view the review: gh pr view <pr-number> --comments or check the PR review file artifact
    • if the review includes recommendations to address before merging, summarize the recommendations and stop
    • if the review ended without critical recommendations, summarize the overall comments and stop