Skip to content
skillsafebeta
← Report library
Purpose / Development

Create Pr Skill Security Audit

What the author says it does (original text)

Create a pull request in the warp repository for the current branch. Use when the user mentions opening a PR, creating a pull request, submitting changes for review, or preparing code for merge.

Independent security check

Security risks found

Files checked
1
Risks found
3
Could it run dangerous commands?Looks for programs run straight after downloading, remote control of your computer, and hidden commands.Risks found: 1
Medium risk

Code PRs execute a repository-controlled script and the full test suite

Source references: 1
What we found

The Skill directly requires running ./script/presubmit and says it executes all unit, documentation, and integration tests. The supplied evidence does not include that script or the tests, so their exact behavior cannot be verified.

Why this matters

Repository scripts, build steps, or tests run with the agent's local permissions; on an untrusted branch they could read accessible files or credentials, use the network, or modify the worktree.

This applies only when a PR contains code changes, and presubmit validation is a normal part of preparing a PR. However, it actively directs execution of a repository-provided script that runs formatting, linting, and all tests. Those scripts and tests execute repository code with the user’s permissions, while their implementations are absent here, so their actual side effects cannot be verified. A user can require inspection of the script and test configuration first, or permit only specifically approved checks.

SKILL.md:32In the instructionsOpen original file
### 2. Run presubmit checks for code changesIf the PR includes code changes, run the relevant presubmit checks before opening or updating it:```bash./script/presubmit````./script/presubmit` runs:- `cargo fmt` - Code formatting- `cargo clippy` - Linting with all warnings as errors- All tests (unit, doc, and integration)If the PR is documentation-only (for example, skills, markdown, or other non-code content), you do not need to run `cargo fmt` or `cargo clippy` just to open or update the PR.
Could it expose your files or keys?Looks for uploads of files containing passwords or keys, and keys written directly in the code.No risks found
Could it delete files or keep running?Looks for broad file deletion, disk overwrites, and programs set to start automatically.Risks found: 1
Medium risk

Unconditional merge of remote master permanently changes the current branch

Source references: 1
What we found

The Skill says to “Always” fetch and merge without first confirming the actual base branch, worktree state, or whether the user wants a merge commit.

Why this matters

It can add a merge commit, modify working-tree files, or create conflicts even when the user only asked to open a PR.

This is an active PR workflow instruction, not merely an example or warning. It always fetches remote content and merges origin/master into the current feature branch, which changes Git state and may create a merge commit or conflicts. Updating from the base is relevant to the stated purpose, but the text does not first verify the repository’s actual base branch, working-tree state, or the user’s acceptance of a merge commit. A user can restrict it to inspection and require confirmation of the base and strategy before merging.

SKILL.md:21In the instructionsOpen original file
### 1. Merge master into your feature branch**Always merge master into your feature branch before starting the review process.**```bashgit fetch origingit merge origin/master```Resolve any merge conflicts locally before opening the PR.
Could it bypass safety checks?Looks for skipped website security checks, excessive file access, or actions that skip your approval.No risks found
Could it mislead the AI or hide text?Checks the skill instructions for requests to ignore you, influence the report, or hide text in invisible characters.No risks found
Could it change links or payment recipients without asking?Looks for forced referral or payment changes combined with instructions to hide the change.Risks found: 1
Medium risk

Fixed co-author trailer can create inaccurate commit attribution

Source references: 1
What we found

The Skill requires a Warp Agent name and email in commits without first verifying the contributor's identity or obtaining the user's approval for that attribution.

Why this matters

If the acting agent is not that identity or the named entity did not make the represented contribution, permanent commit history will misstate authorship, affecting accountability, compliance records, and contribution metrics.

This is an active requirement to add a fixed Warp Agent name and email to commit metadata, avoiding it only when another Warp/Oz co-author trailer already exists. A co-author trailer affects the public attribution of a contribution. The text does not require verifying that this identity made an attributable contribution or obtaining the user’s approval, so it could be misleading when the relationship is inaccurate. A user can require confirmed identity and consent before adding it.

SKILL.md:126In the instructionsOpen original file
### 6. Include co-author attributionWhen committing changes, include attribution as a trailer at the end of the commit message only — never in the PR description — and never add a second Warp/Oz co-author trailer if the commit already has one:```Co-Authored-By: Warp Agent <agent@warp.dev>```

Inside this skill

7 instruction sections

This Skill is an operational guide for creating or updating GitHub pull requests. It directs the agent to synchronize the base branch, run checks, review the diff, and create a draft PR through GitHub CLI.

View source
SKILL.md:21In the instructionsOpen original file
### 1. Merge master into your feature branch**Always merge master into your feature branch before starting the review process.**```bashgit fetch origingit merge origin/master```
SKILL.md:102In the instructionsOpen original file
- **Create a new PR:**  ```bash  # With title and body  gh pr create --title "Title" --body "Description" --draft  # Auto-fill from commits  gh pr create --fill --draft

For PRs containing code, the Skill requires the repository's presubmit script; the document says this runs formatting, linting, and all tests.

View source
SKILL.md:32In the instructionsOpen original file
### 2. Run presubmit checks for code changesIf the PR includes code changes, run the relevant presubmit checks before opening or updating it:```bash./script/presubmit````./script/presubmit` runs:- `cargo fmt` - Code formatting- `cargo clippy` - Linting with all warnings as errors- All tests (unit, doc, and integration)If the PR is documentation-only (for example, skills, markdown, or other non-code content), you do not need to run `cargo fmt` or `cargo clippy` just to open or update the PR.

The Skill recommends querying Linear through an MCP tool and putting the issue ID in the PR title for automatic linking.

View source
SKILL.md:75In the instructionsOpen original file
### 4. Link to Linear taskWhen possible, PRs should be associated with a Linear task. Use the Linear MCP tool (if available) to find corresponding issues.**Branch naming convention:**Remote branches should be prefixed with your name (e.g., `zheng/feature`, `alice/fix-bug`).**How to link PRs to Linear:**Include the issue ID in the PR title (e.g., `[WARP-1234] Add new feature`). Do this **before** creating the PR for automatic linking.

The Skill requires a fixed Warp Agent co-author trailer in commit messages, while instructing the agent not to duplicate an existing Warp/Oz trailer.

View source
SKILL.md:126In the instructionsOpen original file
### 6. Include co-author attributionWhen committing changes, include attribution as a trailer at the end of the commit message only — never in the PR description — and never add a second Warp/Oz co-author trailer if the commit already has one:```Co-Authored-By: Warp Agent <agent@warp.dev>```
Start here · InstructionsSKILL.md
create-pr
Lines connect the instruction file to its sections, not an observed execution order. Select a section to read the source.
Files and check records1 files

Coverage and gaps

Content covered in each file

These are the source ranges included in this check, not a guarantee that every issue has been resolved.

  • SKILL.mdFull text included

This report is for the version above. We read the available code and instructions without running the skill or checking extra packages it installs. This is not a promise of safety: a different version or setup may behave differently.

  • SKILL.mdInstructions

Operations mentioned in code and instructions

Run commands
SKILL.md:25In the instructionsOpen original file
```bashgit fetch origin
SKILL.md:36In the instructionsOpen original file
```bash./script/presubmit
SKILL.md:57In the instructionsOpen original file
```bash# View commits in your branch (comparing against base branch)
Lines read
230
File checksum (to compare versions)
f588d58118d08afb4edaa7f2ea7c771cb88bc2118f680aae1f9f6e1028504ddd