Notre avis
Crée une pull request à partir de la branche courante avec titre, description et options (brouillon, branche cible).
Points forts
- Automatise la création de PR avec des titres et descriptions personnalisés
- Prend en charge les PR en mode brouillon pour les travaux en cours
- Compatibilité avec les styles de flags GitHub CLI et Azure CLI
- Gère les branches source et cible spécifiques
Limites
- Nécessite que l'outil 'aide' soit installé et configuré
- Ne gère pas la validation ou le push des commits avant la création
- Les intégrations spécifiques (GitHub, Azure) dépendent de la configuration
Utilisez cette compétence lorsque vous avez terminé des modifications et souhaitez ouvrir une pull request pour les soumettre à la révision.
Ne l'utilisez pas si vous devez d'abord valider et pousser vos commits, ou si vous utilisez un outil de PR différent non pris en charge par 'aide'.
Analyse de sécurité
SûrThe skill only instructs to run 'aide pr create' with user-provided title and flags. It uses Bash(aide:*) which restricts to aide commands, so no arbitrary shell execution. No destructive or data exfiltration commands are present.
Aucun point d'attention détecté
Exemples
Create a pull request with title 'Add user authentication'Open a PR titled 'PROJ-123: Add OAuth' with description 'Implements OAuth 2.0 with PKCE flow' targeting release/v2.0Create a draft pull request from current branch with title 'WIP: Refactor auth module'name: pr-create description: Create a new pull request. Use when the user wants to open a PR, submit code for review, create a draft PR, or push changes for merge. allowed-tools: Bash(aide:*)
Create Pull Request
Create a new pull request from the current branch.
When to Use
- User says "create a PR" or "open a pull request"
- User wants to submit code for review
- User has finished changes and needs to merge
- User wants to create a draft PR for early feedback
How to Execute
Run:
aide pr create --title "Title" [options]
Flags
Supports both GitHub CLI and Azure CLI style flags:
| Flag (gh-style) | Short | Aliases (az-style) | Description |
|-----------------|-------|-------------------------------------|-------------------------------------------------|
| --title | -t | - | PR title (required) |
| --body | -b | --description | PR description/body |
| --head | -H | --source, -s, --source-branch | Source/head branch (defaults to current branch) |
| --base | -B | --target, --target-branch | Target/base branch (defaults to main) |
| --draft | -d | - | Create as draft PR |
Output Includes
- PR ID and URL
- Title and description
- Source and target branches
- Status (draft or active)
Best Practices
- Use descriptive titles that summarize the change
- Include ticket references in title (e.g., "PROJ-123: Add feature")
- Start as draft if work is incomplete
- Always include a meaningful description
Common Patterns
# Basic PR creation
aide pr create --title "Add user authentication"
# With description
aide pr create --title "PROJ-123: Add OAuth" --body "Implements OAuth 2.0 with PKCE flow"
# Draft PR for early feedback
aide pr create --title "WIP: Refactor auth module" --draft
# Targeting specific branch
aide pr create --title "Hotfix: Login bug" --base release/v2.0
PR Management Workflow
- Prepare branch: Ensure all changes are committed and pushed
- Create PR: Use appropriate flags for title, description, target
- Draft mode: Use
--draftfor work-in-progress - Monitor: Use pr-comments skill to track feedback
- Publish: Use pr-update skill with
--publishwhen ready
Next Steps
After creating a PR:
- Share the PR URL with reviewers
- Use pr-comments skill to monitor feedback
- Use pr-update skill to publish draft when ready
Expert Next.js App Router
Developpement
Un skill qui transforme Claude en expert Next.js App Router.
Générateur de README
Developpement
Crée des README.md professionnels et complets pour vos projets.
Rédacteur de Documentation API
Developpement
Génère de la documentation API complète au format OpenAPI/Swagger.