Skills are in beta. We’re actively improving workflows and setup, so you may see some changes along the way. Feedback welcome!
Use Propel skills to run reviews, fix findings, and triage pull request comments with consistent workflows.
Available skills
| Skill | What it does |
|---|
carl (Coding Agent Review Loop) | Continuously runs Propel code review, fixes valid comments, and re-reviews until no comments remain. |
propel-address-pr-comments | Addresses Propel AI comments in a GitHub pull request review. |
propel-code-review | Runs async diff-based code reviews with the Propel Review API and retrieves comments and feedback. |
Before you install skills
Set PROPEL_API_KEY in your environment.
Create a Review API token from Review API Tokens.
export PROPEL_API_KEY="rev_..."
To persist this value in your shell profile:
# bash
echo 'export PROPEL_API_KEY="rev_..."' >> ~/.bashrc && source ~/.bashrc
# zsh
echo 'export PROPEL_API_KEY="rev_..."' >> ~/.zshrc && source ~/.zshrc
If you skip this step, the skill may prompt you to generate a token when it runs.
Install by coding agent
Run this command in Codex:$skill-installer propel-gtm/propel-code-skills
Run these commands in Claude Code:/plugin marketplace add propel-gtm/propel-code-skills
/plugin install propel-code-review@propel-code-skills
/plugin install carl@propel-code-skills
Cursor supports skills through folders that contain SKILL.md.Project-scoped install (recommended):mkdir -p .cursor/skills
cp -R plugins/propel-code-review/skills/propel-code-review .cursor/skills/
cp -R plugins/carl/skills/carl .cursor/skills/
cp -R plugins/propel-code-review/skills/propel-address-pr-comments .cursor/skills/
User-scoped install:mkdir -p ~/.cursor/skills
cp -R /path/to/propel-code-skills/plugins/propel-code-review/skills/propel-code-review ~/.cursor/skills/
cp -R /path/to/propel-code-skills/plugins/carl/skills/carl ~/.cursor/skills/
cp -R /path/to/propel-code-skills/plugins/propel-code-review/skills/propel-address-pr-comments ~/.cursor/skills/
Prompt your agent to use the skills
For a diff review workflow:
Use `propel-code-review` to review the diff from base branch to HEAD, then report any findings before final output.
For an automatic review and fix loop:
Use `carl` to repeatedly run `propel-code-review` and address valid comments until none remain.
For PR-specific finding triage:
Use `propel-address-pr-comments` to find the open PR for the current branch, fetch Propel findings, ask which comments to address, and apply fixes for selected findings.
Next steps
- Open How to interact with Propel to run your first review commands.
- Open Knowledge base to add reusable team rules.