Skills git-pushing
๐Ÿ“ฆ

git-pushing

Content revision r2 Medium Risk โš™๏ธ External commands

Commit and Push Git Changes

Committing and publishing routine changes can require several Git commands. This skill stages all changes, creates one commit, and pushes the current branch.

Supports: Claude Codex Code(CC)
๐Ÿ“Š 67 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-pushing" from https://skillstore.io/skills/sickn33-git-pushing.md and its manifest at https://skillstore.io/api/skills/sickn33-git-pushing/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-pushing". Commit and push with the message fix: handle empty search results.

Expected outcome:

All unignored changes were committed and the current branch was pushed to origin.

Using "git-pushing". Push my current work using the default message.

Expected outcome:

The changes were committed as chore: update code and the branch was pushed with upstream tracking.

Using "git-pushing". Push these changes when origin rejects the branch.

Expected outcome:

The push failed, and the script stopped with the Git error for manual resolution.

Security Audit

Medium Risk
v5 โ€ข 7/23/2026 Open versioned report

The five static alerts are false positives because they identify code fences, an interpreter declaration, and a hardcoded Git branch lookup. The workflow still has medium operational risk because it stages every unignored change and pushes to origin without review or confirmation.

2
Files scanned
61
Lines analyzed
0
Review items
0
False positives ignored

Confirmed security concerns (1)

Medium
Unreviewed Bulk Commit and Remote Push
The script stages every unignored change, commits it, and pushes the current branch to origin without a diff review or confirmation. This can publish secrets, unrelated files, or unintended code.
The code directly runs git add, git commit, and git push in sequence. No review or confirmation step appears between these operations.
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-pushing/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-pushing/security.svg)](https://skillstore.io/skills/sickn33-git-pushing?utm_source=security_passport_badge)

HTML badge

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

Embed card

<iframe src="https://skillstore.io/embed/skills/sickn33-git-pushing.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-pushing security audit report (audit version 5) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-git-pushing/audits/5

BibTeX citation

@techreport{sickn33-sickn33-git-pushing-2026, author = {sickn33}, title = {git-pushing security audit report (audit version 5)}, institution = {Skillstore}, year = {2026}, number = {5}, url = {https://skillstore.io/skills/sickn33-git-pushing/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-pushing 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-pushing/audits/5" identifiers: - type: other value: "skillstore:sickn33-git-pushing:audit:5" description: "Skillstore immutable audit report identifier"

Skillstore Score

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

What You Can Build

Publish a Small Fix

Commit and push a completed fix from the current branch.

Share Team Progress

Push a reviewed feature branch with a specific conventional commit message.

Automate Routine Updates

Publish generated or maintenance changes through a consistent Git command sequence.

Try These Prompts

Push Current Work
Commit and push my current changes using the default message.
Use a Commit Message
Commit and push all current changes with the message fix: correct login redirect.
Publish a Feature Branch
Push this feature branch with the message feat: add account export.
Complete a Reviewed Release Update
Commit and push the reviewed release changes with the message chore: prepare version 2.4.0.

Best Practices

  • Inspect Git status and the complete diff before invoking the skill.
  • Ensure .gitignore excludes credentials, local configuration, and generated files.
  • Provide a specific conventional commit message that describes the reviewed changes.

Avoid

  • Do not run the skill with unrelated or unreviewed worktree changes.
  • Do not use it when the current branch or origin remote is uncertain.
  • Do not expect it to resolve hooks, conflicts, authentication, or branch protection failures.

Frequently Asked Questions

Which files does the skill stage?
It stages every unignored change under the current repository.
Can I provide a commit message?
Yes. Supply the complete message when requesting the commit and push.
What message is used by default?
The script uses chore: update code when no message is provided.
Which branch is pushed?
The script detects and pushes the currently checked-out branch.
Which remote receives the push?
The script always pushes to the remote named origin.
Does the skill run tests or review changes?
No. Review the diff and run required validation before invoking it.

Developer Details

Author

sickn33

License

MIT

Skillstore revision

r2

Version notice

The author did not declare a version.

Ref

88a8e9a07f4c54ab105c1c41b6267c287146b07b

Maintenance freshness

7/26/2026

Usage

8 downloads ยท 124 views

File structure

๐Ÿ“ scripts/

๐Ÿ“„ smart_commit.sh

๐Ÿ“„ SKILL.md