pr

Engineering Community

Skill notes

Step 1: Check branch

Run git branch --show-current. If on main, tell the user they cannot create a PR from the main branch and stop. Run git log main..HEAD --oneline to check for commits ahead of main. If there are no commits AND the working directory is clean, tell the user there is nothing to create a PR for and stop.

Step 2: Check working directory

Run git status to check if the working directory is clean. Clean: Proceed to Step 3. Dirty (any staged, unstaged, or untracked changes): Ask the user: Commit changes first — suggest using /ci, then stop and let the user run it. Ignore local changes and continue creating the PR based on existing commits only.

Step 3: Push and create PR

Run git push -u origin HEAD to push the branch. Run git log main..HEAD to analyze all commits on this branch. Generate a succinct, self-explanatory PR description from them. Run gh pr create with a title following Conventional Commits pattern. Base branch is main.

Step 4: Request review agents

After the PR is created, automatically request code review from available review agents: Run gh pr edit --add-reviewer @copilot to request Copilot code review. If the command succeeds, note that Copilot review has been requested. If it fails (e.g., Copilot not available for the repo), skip silently and continue.

Step 5: Show result

Display the PR URL to the user, along with the review request status.

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Engineering
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@tomevault-io · no license declared
Token usage
Lean
Setup complexity
Plug-and-play
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

Output preview pr-tomevault-io.preview
# Step 5: Show result

Display the PR URL to the user, along with the review request status.

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.