Skills git-pr-workflows-git-workflow
📦

git-pr-workflows-git-workflow

Content revision r2 Medium Risk ⚙️ External commands

Orchestrate Git and Pull Request Workflows

Complex Git changes can reach review without consistent testing, commit structure, or deployment checks. This skill organizes review, validation, commits, branches, and pull request preparation.

Supports: Claude Codex Code(CC)
📊 70 Adequate

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request
Review the Skillstore skill "git-pr-workflows-git-workflow" from https://skillstore.io/skills/sickn33-git-pr-workflows-git-workflow.md and its manifest at https://skillstore.io/api/skills/sickn33-git-pr-workflows-git-workflow/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/sickn33-git-pr-workflows-git-workflow.md Signed manifest GET /api/skills/sickn33-git-pr-workflows-git-workflow/manifest Signed lockfile GET /api/skills/sickn33-git-pr-workflows-git-workflow/lockfile

Test it

Using "git-pr-workflows-git-workflow". Review a payment retry change before opening a pull request.

Expected outcome:

  • Review summary: one high-risk duplicate-charge path requires resolution.
  • Testing: unit coverage exists, but an integration test for repeated timeouts is missing.
  • Recommendation: block the pull request until retry idempotency and integration coverage are verified.

Using "git-pr-workflows-git-workflow". Plan commits for an authentication timeout fix and related tests.

Expected outcome:

  • Recommended structure: one fix commit for timeout handling and one test commit for regression coverage.
  • Primary scope: authentication.
  • Breaking change: none identified from the supplied change summary.

Using "git-pr-workflows-git-workflow". Prepare a draft pull request summary for a database migration.

Expected outcome:

  • Summary: adds the migration and preserves compatibility during deployment.
  • Validation: migration tests pass, while rollback timing still needs staging verification.
  • Deployment note: apply the migration before enabling dependent application behavior.

Security Audit

Medium Risk
v5 • 7/23/2026 Open versioned report

All 11 static findings are false positives caused by Markdown inline code around flags, a file path, a documented command, and a naming pattern. No prompt injection, reconnaissance, or executable Ruby or shell backtick behavior appears in SKILL.md. A medium-risk concern remains because the workflow can lead agents toward remote repository mutations without a mandatory confirmation gate.

1
Files scanned
149
Lines analyzed
0
Review items
0
False positives ignored

Confirmed security concerns (1)

Medium
SKILL.md:86-111
Remote Repository Mutations Lack Confirmation Gate
The workflow prepares pushes, direct main changes, pull request metadata, and auto-merge without requiring human confirmation. This could cause unintended remote repository changes.
The branch and pull request phases explicitly cover push preparation, direct main pushes, metadata changes, and auto-merge. No mandatory approval gate is stated.

Risk Factors

⚙️ External commands (10)
SKILL.md:30 SKILL.md:37 SKILL.md:38 SKILL.md:39 SKILL.md:40 SKILL.md:41 SKILL.md:42 SKILL.md:43 SKILL.md:130 SKILL.md:139
Audited by: codex View Audit History →
Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report
Security Assessment

Copy report link

https://skillstore.io/skills/sickn33-git-pr-workflows-git-workflow/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/sickn33-git-pr-workflows-git-workflow/security.svg)](https://skillstore.io/skills/sickn33-git-pr-workflows-git-workflow?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/sickn33-git-pr-workflows-git-workflow?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-git-pr-workflows-git-workflow/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/sickn33-git-pr-workflows-git-workflow.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>
Academic citations (APA · BibTeX · CFF)

APA citation

sickn33. (2026). git-pr-workflows-git-workflow security audit report (audit version 5) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-git-pr-workflows-git-workflow/audits/5

BibTeX citation

@techreport{sickn33-sickn33-git-pr-workflows-git-workflow-2026, author = {sickn33}, title = {git-pr-workflows-git-workflow security audit report (audit version 5)}, institution = {Skillstore}, year = {2026}, number = {5}, url = {https://skillstore.io/skills/sickn33-git-pr-workflows-git-workflow/audits/5}, note = {Author version unspecified} }

CITATION.cff

cff-version: 1.2.0 message: "If you use this Skill, cite its author and this versioned security audit report." title: "git-pr-workflows-git-workflow security audit report (audit version 5)" version: "unspecified" type: report authors: - name: "sickn33" date-released: "2026-07-23" url: "https://skillstore.io/skills/sickn33-git-pr-workflows-git-workflow/audits/5" identifiers: - type: other value: "skillstore:sickn33-git-pr-workflows-git-workflow:audit:5" description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: High
55
Architecture
85
Maintainability
87
Content
69
Community
83
Spec Compliance

What You Can Build

Prepare a Feature Pull Request

A software developer uses staged reviews, tests, commit guidance, and branch checks before opening a pull request.

Standardize Repository Reviews

A repository maintainer applies consistent quality, security, compatibility, and reviewer checks across incoming changes.

Assess Release Readiness

A release engineer combines test results, breaking-change analysis, branch policy, and rollback planning before merge.

Try These Prompts

Review Changes Before a Pull Request 
Review my uncommitted changes for a pull request targeting [branch]. Identify quality issues, missing tests, and breaking changes. Do not modify files or push.
Plan Conventional Commits 
Prepare a Conventional Commit plan for [change summary]. Recommend atomic commits, scopes, subjects, and any breaking-change footer after reviewing the current diff.
Run Staged Validation 
Run the staged validation workflow for [target branch]. Review changes, execute available tests, report coverage gaps, verify branch readiness, and stop before remote actions.
Prepare a Draft Pull Request 
Prepare a draft pull request for [change]. Include review findings, test evidence, migration needs, deployment notes, rollback steps, labels, and reviewer recommendations. Request approval before any remote action.

Best Practices

  • Confirm the target branch, repository policies, and remote action permissions before starting.
  • Resolve critical and high-severity findings before creating commits or pull requests.
  • Preserve test evidence, breaking-change notes, and rollback details in the pull request.

Avoid

  • Do not skip tests without documenting the reason and residual risk.
  • Do not push, rewrite history, enable auto-merge, or modify remote metadata without explicit approval.
  • Do not claim coverage, CI readiness, or branch protection compliance without verified results.

Frequently Asked Questions

Does this skill create pull requests automatically?
It can guide or coordinate pull request creation. Remote actions depend on available tools and should require explicit approval.
Which development strategies does it support?
It covers feature-branch and trunk-based workflows, with configurable draft, squash, conventional commit, test, and no-push options.
Does it execute tests?
It instructs a testing agent to run available suites and report coverage. Results depend on the repository and host environment.
Can it generate commit messages?
Yes. It categorizes changes and prepares Conventional Commit messages, including scopes, rationale, issue references, and breaking-change notes.
Does the skill modify repository files?
The skill contains instructions rather than scripts. Authorized host agents may execute repository commands while following the workflow.
Is the referenced implementation playbook included?
No. The published file structure contains only SKILL.md, so the referenced playbook is unavailable.

Developer Details

Author

sickn33

License

MIT

Skillstore revision

r2

Version notice

The author did not declare a version.

Repository

https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/git-pr-workflows-git-workflow

Ref

88a8e9a07f4c54ab105c1c41b6267c287146b07b

Maintenance freshness

7/26/2026

Usage

11 downloads · 111 views

File structure

📄 SKILL.md