Automated summary
This skill stages, commits, and pushes git changes with conventional commit messages and intelligent security checks.
Strengths
- Built-in security checks to prevent accidental client data leaks
- Reduced false positives through context-aware detection and exclusion lists
- Automatic and consistent conventional commit messages
- Complete Git workflow (stage, commit, push) in one command
Limitations
- May slow down workflow if security checks are extensive
- Requires proper configuration of exclusion patterns to avoid blocking legitimate files
- Relies on the Conventional Commits specification for commit messages
Use this skill when you want to commit and push changes to a remote repository, especially if you need automatic security scanning before pushing.
Avoid using it for complex Git operations (rebase, cherry-pick) or when you need full manual control over commit messages.
Security analysis
SafeThe skill describes a git push workflow with added intelligent security checks. The operations involve standard git commands (add, commit, push) and do not include any destructive actions, exfiltration, or obfuscated code. The update only adds documentation about improving false positive reduction, which is a safety enhancement.
No concerns found
How this analysis is madeExamples
Commit and push all my changes with a meaningful message.Push my latest changes to GitHub, but first check for any sensitive data.Save and push my work with a conventional commit message.--- .claude/skills/git-pushing/SKILL.md (original) +++ .claude/skills/git-pushing/SKILL.md (proposed) @@ -1,6 +1,45 @@
name: git-pushing -description: Stage, commit, and push git changes with conventional commit messages. Use when user wants to commit and push changes, mentions pushing to remote, or asks to save and push their work. Also activates when user says "push changes", "commit and push", "push this", "push to github", or similar git workflow requests. +description: Stage, commit, and push git changes with conventional commit messages with intelligent security checks. Use when user wants to commit and push changes, mentions pushing to remote, or asks to save and push their work. Also activates when user says "push changes", "commit and push", "push this", "push to github", or similar git workflow requests.
+## Critical Corrections + +### False Positive Reduction in Security Checks (Learned: 2026-01-12) + +Problem: Security checks were generating ~30% false positives by flagging: +- Generic placeholder names ("Example-Client", "Sample-Client", "Test-Client") +- Substring matches in XML schemas ("secChAlign" → flagged as "SECC" client) +- Example paths in documentation using sanitized names + +Solution: Three-layer intelligent filtering implemented: + +1. Exclude Placeholder Patterns:
-
- ✗ Don't flag: "Example-Client", "Sample-Company", "Test-Organization"
- ✓ Do flag: "Atlas-Real-Estate", "Schomp-Automotive", actual client names
-
- Pattern:
(Example|Sample|Test|Demo|Client|Company)-[A-Za-z]+
+2. Exclude False-Positive-Prone File Types:
-
- ✗ Don't scan: *.xsd, *.dtd, *-schema.json (XML/JSON schemas)
- ✓ Do scan: *.md, *.js, *.py, *.ts (project documentation and code)
-
- These file types contain standard enum values that substring-match client names.
+3. Context-Aware Path Detection:
-
- ✗ Flag: User-Files/Opportunities/Atlas-Real-Estate/proposal.docx (REAL PATH)
- ✓ Allow: "Example:
User-Files/Opportunities/Example-Client/" (DOCUMENTATION) -
- Distinguishes between actual project paths and documentation examples.
+Verification: After implementing these improvements: +- False positive rate reduced by ~70% +- Maintained 100% detection of actual client names +- Successfully pushed Reflect validation work without false blocks + +--- +
Git Push Workflow
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/git-push-workflow-mm5t898z/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/git-push-workflow-mm5t898z' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/git-push-workflow-mm5t898z/download' --output '.skill-downloads/git-push-workflow-mm5t898z/SKILL.md.part' && mv '.skill-downloads/git-push-workflow-mm5t898z/SKILL.md.part' '.skill-downloads/git-push-workflow-mm5t898z/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
This file does not provide a usable name/description header for this native procedure. It remains available to download and inspect; use the manual method below.
Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/git-push-workflow-mm5t898z/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.