git-workflow
Standardize Git Commits and Pull Requests
Inconsistent commits and pull requests slow reviews and create unclear history. This skill provides practical formats, checklists, and Git workflow guidance.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "git-workflow" from https://skillstore.io/skills/cain96-git-workflow.md and its manifest at https://skillstore.io/api/skills/cain96-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.
Test it
Using "git-workflow". Added JWT token refresh handling and tests for expired sessions.
Expected outcome:
Suggested commit: feat(auth): add JWT token refresh. The body explains expiry handling and test coverage.
Using "git-workflow". Prepare a pull request for a new profile endpoint that closes issue 123.
Expected outcome:
A conventional feature title, concise summary, endpoint change list, test checklist, breaking-change statement, and issue closure reference.
Using "git-workflow". Clean three local commits containing one feature and two follow-up fixes.
Expected outcome:
Recommended workflow: create a backup branch, start an interactive rebase, squash fixups, review the result, then push only with approval.
Security Audit
SafeAll 48 static findings are false positives caused by Markdown formatting, documented Git examples, a public standards link, or ordinary checklist text. The skill contains no executable scripts, prompt injection, credential access, covert network behavior, or malicious intent. Its Git examples can modify repositories when followed, so users should review commands before execution.
Risk Factors
⚙️ External commands (42)
🌐 Network access (1)
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.
Copy report link
https://skillstore.io/skills/cain96-git-workflow/audits/9?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/cain96-git-workflow?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/cain96-git-workflow?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/cain96-git-workflow/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/cain96-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
Cain96. (2026). git-workflow security audit report (audit version 9) [Author version unspecified]. Skillstore. https://skillstore.io/skills/cain96-git-workflow/audits/9BibTeX citation
@techreport{cain96-cain96-git-workflow-2026,
author = {Cain96},
title = {git-workflow security audit report (audit version 9)},
institution = {Skillstore},
year = {2026},
number = {9},
url = {https://skillstore.io/skills/cain96-git-workflow/audits/9},
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-workflow security audit report (audit version 9)"
version: "unspecified"
type: report
authors:
- name: "Cain96"
date-released: "2026-07-23"
url: "https://skillstore.io/skills/cain96-git-workflow/audits/9"
identifiers:
- type: other
value: "skillstore:cain96-git-workflow:audit:9"
description: "Skillstore immutable audit report identifier"
Compare variants
7 installable variantsEach author remains a separate installable skill. The recommended variant is ranked by Skillstore evidence.
Why this variant is first
atman36-git-workflow
2026-08-21
89jobrien-git-workflow
2026-08-21
doyajin174-git-workflow
2026-08-21
barnhardt-enterprises-inc-git-workflow
2026-08-21
cain96-git-workflow
2026-08-21
0xdarkmatter-git-workflow
2026-08-21
supercent-io-git-workflow
2026-08-21
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Prepare focused commits
Turn a change summary into a clear conventional commit with an appropriate type, scope, body, and trailer.
Draft review-ready pull requests
Create a concise title, change summary, test plan, breaking-change note, and related issue references.
Maintain clean repository history
Plan rebases, cherry-picks, stashes, and bisects while keeping operations explicit and reviewable.
Try These Prompts
Create a conventional commit message for these changes: [summary]. Choose an appropriate type and scope, then explain the reason when needed.
Draft a pull request for [changes]. Include a conventional title, summary, change list, test plan, breaking changes, and related issues.
Propose a safe interactive rebase plan for these commits: [commit list]. Identify commits to reorder, reword, squash, or preserve.
Design a Git bisect workflow for [regression]. Define good and bad revisions, the verification test, recovery steps, and expected evidence.
Best Practices
- Review repository status and staged changes before creating a commit.
- Confirm branch protection and team policy before rebasing or force pushing.
- Replace every placeholder with verified project details before running commands.
Avoid
- Do not run history-rewriting commands on shared branches without coordination.
- Do not copy placeholder hashes, issue numbers, names, or addresses into real commands.
- Do not treat passing checklists as proof that code is secure or correct.