AgentStack
SKILL verified MIT Self-run

Create Pr

skill-jeffsenso-prestashop-skills-create-pr · by jeffsenso

>

No reviews yet
0 installs
10 views
0.0% view→install

Install

$ agentstack add skill-jeffsenso-prestashop-skills-create-pr

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Create Pr? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Create a PrestaShop Pull Request

Purpose

Guide a contributor through creating a pull request that complies with the PrestaShop contribution guidelines, including the mandatory metadata table.

Steps

1. Gather context

  • Read the PR template from .github/PULL_REQUEST_TEMPLATE.md — this is the single source of truth for the table format.
  • Run git log and git diff against the target branch to understand what changed.
  • Identify the target branch from git (see branching rules in .ai/CONTEXT.md).

2. Auto-fill fields

From code analysis and git context, infer as much as possible:

| Field | How to infer | |-------|-------------| | Branch | Current git branch or merge target | | Description | Summarize from commits and diff. Be specific (versions, browser/server config, module/theme). | | Type | bug fix · improvement · new feature · refacto — infer from changes | | Category | FO · BO · CO · IN · WS · TE · LO · ME · PM — infer from files changed. See category reference. | | BC breaks | Analyze public API changes → yes / no | | Deprecations | Check for new @deprecated annotations → yes / no | | How to test | Write step-by-step verification instructions from the PR context | | Fixed issue | Extract from conversation, branch name (e.g. fix/12345), or commit messages. Format: Fixes # |

3. Ask before guessing

For any required field (Branch, Description, Type, Category, BC breaks, Deprecations) that cannot be confidently determined, ask the user. Do not guess.

Optional fields (UI Tests, Related PRs, Sponsor company) — fill when known, leave the template placeholder otherwise.

4. Create the PR

Use GitHub MCP tools (mcp__github__create_pull_request) or gh pr create CLI to create the PR with the filled-in template as the body.

Output

The created PR URL, displayed to the user.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Versions

  • v0.1.0 Imported from the upstream source.