AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Create Pr

skill-makigjuro-cloudstack-ai-plugins-create-pr · by makigjuro

Create a pull request with a structured description linking to the GitHub issue. Use when ready to push and open a PR -- auto-detects changed services/layers and generates a structured PR body with test plan.

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

Install

$ agentstack add skill-makigjuro-cloudstack-ai-plugins-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.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-makigjuro-cloudstack-ai-plugins-create-pr)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
1mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
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 Pull Request

Create a pull request for the current branch with a structured description.

Configuration

Read cloudstack.json from the project root at the start of execution. Extract relevant fields:

  • REPO_OWNER / REPO_NAME = repository.owner / repository.name (default: detect from git remote -v)
  • SOLUTION = backend.solutionPath (default: find *.sln)
  • FRONTEND_PATH = frontend.path (default: web)
  • CHARTS_PATH = infrastructure.chartsPath (default: deploy/charts)
  • TF_PATH = infrastructure.terraformPath (default: infra/terraform/modules)

If cloudstack.json does not exist, auto-detect by scanning the project structure and parsing the GitHub remote URL.

Arguments

  • {issue} -- GitHub issue number to link (optional). If not provided, attempt to extract from the branch name.

Prerequisites

  • You must be on a feature branch (not main)
  • All changes should be committed (warn if working tree is dirty)
  • Branch should have at least one commit ahead of main

Process

  1. Gather context:
  • git status -- check for uncommitted changes, warn if dirty.
  • git log origin/main..HEAD --oneline -- list all commits on this branch.
  • git diff origin/main...HEAD --stat -- summary of changed files.
  • Extract issue number from branch name or argument.
  1. Analyze changes:
  • Identify which layers were modified (Domain, Application, Infrastructure, Host, Frontend, Tests).
  • Detect affected services by checking paths against known service directories:

``bash git diff origin/main...HEAD --name-only | grep -oP 'src/\K[^/]+' | sort -u ``

  • Detect what was added vs changed vs removed from the diff stat.
  • Check if documentation may need updating (new endpoints, entities, or events).
  1. Push and create PR:
  • Push the branch to origin with -u flag.
  • Create the PR using MCP.

PR Body Format

## Summary
{1-3 bullet points describing what this PR does}

Closes #{issue-number}

## Affected Services
{List only services that were actually modified}

## Changes
- **Domain:** {changes or "No changes"}
- **Application:** {changes or "No changes"}
- **Infrastructure:** {changes or "No changes"}
- **Endpoints:** {changes or "No changes"}
- **Frontend:** {changes or "No changes"}
- **Tests:** {changes or "No changes"}

## Test Plan
- [ ] Unit tests pass
- [ ] Integration tests pass (if applicable)
- [ ] Frontend lint clean (if applicable)
- [ ] Frontend type-check clean (if applicable)
- [ ] Helm lint clean (if applicable)
- [ ] Terraform validate clean (if applicable)
- [ ] Architecture check passes
- [ ] {Any feature-specific manual verification steps}

Generated with [Claude Code](https://claude.com/claude-code)

Commands

# Push branch
git push -u origin HEAD

Create the PR using MCP for structured creation:

mcp__github-mcp-server__create_pull_request(
  owner: "{REPO_OWNER}",
  repo: "{REPO_NAME}",
  title: "{title}",
  body: "{body}",
  head: "{branch-name}",
  base: "main"
)

Error Handling

  • No commits ahead of main: Warn the user -- there's nothing to PR.
  • Push fails (no upstream): Use git push -u origin HEAD to set the upstream.
  • PR already exists: Check with gh pr list --head {branch} and report the existing PR URL instead of creating a duplicate.

Guidelines

  • Keep the PR title under 70 characters, in imperative mood ("Add user group assignments", not "Added").
  • Use Closes #{issue} to auto-close the linked issue on merge.
  • If the branch has many commits, suggest the user consider squashing before creating the PR.
  • Report the PR URL when done.

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.