← Browse

@llloooggg/pr

B

Create a PR from dev to main following project merge flow. Runs version bump, syncs dev with main first, creates PR with --auto merge.

skillclaude

Install

agr install @llloooggg/pr --target claude

Writes 1 file into .claude/skills/, pinned to git-3b9c85b4.

  • .claude/skills/pr/SKILL.md

Document


name: pr description: Create a PR from dev to main following project merge flow. Runs version bump, syncs dev with main first, creates PR with --auto merge.

PR workflow for LetsFLUTssh (dev -> main)

Follow the project's branching & release flow strictly.

Step 1: Verify state

  • Confirm we're on dev branch. If not, STOP
  • git status — working tree must be clean. If dirty, STOP and tell user to commit first

Step 2: Sync dev with main

git fetch origin main && git merge origin/main

If conflicts: STOP and tell user. If fast-forward or clean merge, push: git push

Step 3: Version bump

Run the bump script to calculate and apply the version bump from conventional commits:

dev/scripts/bump-version.sh
  • If it says "nothing to bump" — skip (docs/test/ci-only PR, no version change needed)
  • If it bumps — push the bump commit: git push

Step 4: Gather PR info

  • git log origin/main..HEAD --oneline — all commits going into this PR
  • git diff origin/main...HEAD --stat — changed files summary

Step 5: Create PR with auto-merge

gh pr create --base main --head dev --title "TITLE" --body "$(cat <<'EOF'
## Summary
- bullet points from commits

## Test plan
- CI passes (ci, osv-scan, semgrep-scan, codeql-scan)
EOF
)" && gh pr merge --auto --merge

Step 6: After merge confirmation

Tell user: "After PR merges, sync dev with main: git fetch origin main && git merge origin/main && git push"

Arguments

If user passes a custom title: $ARGUMENTS

Trustgrade B

  • passBody integrity

    Whether the stored document is plausibly the kind of file the artifact declares, rather than something fetched by mistake.

  • passType matchnot applicable to this artifact type

    Whether the artifact is really the kind of thing its metadata claims it is.

  • passFreshness

    How long since the source repository was last pushed to.

  • passPrompt injection

    Scans the artifact's own text for instructions aimed at your agent rather than at you.

  • warnLicensecopyleft/unknown — index-and-link only

    Whether the source repository declares an SPDX license permissive enough to redistribute.

How the grade is calculated

Each check contributes 0 points when it passes, 1 when it warns, and 2 when it fails. The total maps to a letter:

  • Aevery check passed
  • Bone warning
  • Ctwo warnings
  • Dprompt injection or body integrity failed, or three warnings
  • Fone of those failed, and something else is wrong

These are automated hygiene checks, not a security audit, and not a dependency or vulnerability scan. A grade of A means nothing was flagged — not that the artifact is safe.

Versions

  • git-3b9c85b458e92026-07-31