dneprokos/git-push-creator
.cursor/skills/git-push-creator/SKILL.md
Push the current local branch to `origin` using the same branch name on the remote. Use when the user asks to push the current branch or publish local commits. If the current branch is the resolved core branch (`main` or `develop`), abort and return a safety message.
$ install --global
skillsauthnpx skillsauth add dneprokos/skills-examples git-push-creatorInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 16, 2026, 2:39 AM4.5s3 files scanned
SKILL.md
- name:
- git-push-creator
- description:
- >-
- argument-hint:
- optional push context
Git Push Creator
Push the current branch to origin safely.
When this skill fits
Use it for requests like:
- "push my current branch"
- "publish this branch to origin"
- "push local commits to remote"
Do not use it for:
- pushing the core branch (
mainordevelop) - force pushing
- deleting remote branches
- opening pull requests
Workflow
1. Detect the current branch
Check the current local branch name first.
Resolve the core branch first (main preferred, then develop).
If the branch matches that resolved core branch, stop immediately and return:
You cannot push to the <core-branch> branch with this skill.
2. Use the same branch name on remote
Push the local branch to origin using the same branch name remotely.
Example:
pwsh -NoProfile -File ./.github/skills/git-push-creator/scripts/push-branch.ps1
The helper script will:
- confirm the workspace is a Git repository
- detect the current branch
- resolve the core branch (
mainthendevelop) - abort if the current branch matches the resolved core branch
- push to
origin/<same-branch-name> - set upstream if needed
3. Return the exact git result
Do not guess success. Return the real git output after the push completes.
Hard rules
- Never push the resolved core branch (
mainordevelop) with this skill. - Never rename the remote branch; it must match the local branch name.
- Do not use
--forceor--force-with-leaseunless the user explicitly requests it. - Return the exact git result instead of summarizing vaguely.
Related Skills
dneprokos/windows-secretmanagement-setup
data-ai
VerifiedTrustedCommunity
Install and configure Windows Credential Manager style secret storage for PowerShell using SecretManagement and SecretStore. Use when users ask to install secret manager support, set up Credential Manager for GitHub token storage, or bootstrap GitHubToken for PR skills.
2SKILL.mdUpdated Apr 16, 2026
dneprokos/ut-coder
development
VerifiedTrustedCommunity
Generate a complete, compilable unit test file from an Analyst test plan and Architect strategy. Uses AAA pattern, language-specific frameworks (NUnit, JUnit 5, pytest, Vitest), correct mock/real dependency instantiation, constructor null-guard tests, parameterized tests, and setup/teardown hooks. Input is the Analyst JSON plan plus Architect strategy summary. Use when asked to generate test code, write test implementation, create test file, or implement tests from a plan. Also invoked as Phase 3 by the unit-test-generator agent.
2SKILL.mdUpdated Apr 16, 2026
dneprokos/ut-architect
development
VerifiedTrustedCommunity
Define the mocking strategy and assertion style for a unit test plan. Classifies each dependency as mock or real, resolves assertion framework and test file location from project patterns, lists constructor null-guard tests with expected exception types, and specifies abstraction interfaces for non-deterministic calls. Input is a JSON test plan from ut-analyst. Use when asked to define mocking strategy, plan test architecture, classify dependencies as mock vs real, or design test structure. Also invoked as Phase 2 by the unit-test-generator agent.
2SKILL.mdUpdated Apr 16, 2026
dneprokos/ut-analyst
testing
VerifiedTrustedCommunity
Analyze a class or function and produce a structured JSON test plan. Classifies all dependencies (interface, abstract, valueObject, dto, primitive), detects non-deterministic calls, enumerates test cases using black-box techniques (Equivalence Partitioning, Boundary Value Analysis, Decision Table, State Transition), and lists constructor null-guard requirements. Use when asked to analyze a class for testing, create a test plan, classify dependencies, or produce test case inventory. Also invoked as Phase 1 by the unit-test-generator agent.
2SKILL.mdUpdated Apr 16, 2026