skill-urmzd-dotfiles-pr · by Install
$ agentstack add skill-urmzd-dotfiles-pr ✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.
Security review
✓ PassedNo 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.
Verified badge
Passed review? Show it. Paste this badge into your README — it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-urmzd-dotfiles-pr) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming — see below.
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 →About
PR
Create a pull request with a well-structured summary.
Steps
- Gather context:
- Detect the default branch:
gh repo view --json defaultBranchRef -q .defaultBranchRef.name - Get all commits since divergence:
git log ..HEAD --oneline - Get the full diff:
git diff ...HEAD --stat - Check if the branch is pushed:
git rev-list @{u}..HEAD --count 2>/dev/null
- Push if needed: If there are unpushed commits, run
git push -u origin HEAD.
- Generate PR content:
- Title (if not provided): Derive from commits. If single commit, use its message. If multiple, summarize the theme (under 70 chars).
- Body: Use this format:
```text ## Summary
## Test plan
- [ ]
```
- Create PR: Run
gh pr create --title "" --body ""using a HEREDOC for the body.
- Report: Show the PR URL.
Rules
- Never create a PR if there are no commits ahead of the default branch.
- If a PR already exists for this branch, show its URL instead of creating a duplicate.
- Keep the title under 70 characters.
- Group commits by type (feat, fix, chore, etc.) in the summary.
Gotchas
- Refuse when
HEADis the default branch: a PR needs a non-default source branch. Detect the default withgh repo view --json defaultBranchRef -q .defaultBranchRef.name, compare togit branch --show-current, and if they match, stop and tell the user to create a feature branch first. - For a fork-based PR, the head ref must be qualified as
owner:branch. Pass it withgh pr create --head :(the owner is the fork's GitHub login), so the PR targets the upstream repo from your fork.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: urmzd
- Source: urmzd/dotfiles
- License: Apache-2.0
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet — be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.