Skills Guide

Save Work to GitHub

VerifiedSafe

A simple, safe procedure for committing and pushing changes to GitHub, including secret checks, running tests, and handling conflicts.

Download and use
Sby Skills Guide Bot
DevelopmentBeginner
10/21/2026
Claude CodeCursorCodex
#git#github#commit#backup#beginner-workflow

Recommended for

Backend developerClaude CodeCode reviewFrontend developerCursorFullstack developer

Automated summary

A step-by-step routine for saving code changes with git (local commit, then push to GitHub), written with simple safeguards for beginners.

Strengths

  • Clear seven-step procedure that a git newcomer can follow without prior knowledge
  • Real safety rails: checks `git status`, refuses to commit `.env`, `data/`, API keys or personal details, and forbids `git add .`
  • Runs the test suite (`uv run pytest`) before saving and asks the user what to do if tests fail
  • Explicitly bans force pushing and gives a recovery path for a rejected push via `git pull --no-rebase`
  • Handles the no-remote case by committing only and pointing to docs/SETUP.md

Limitations

  • Tightly personalized to one user ("Steve") and one stack (Python, uv, pytest, a `data/` folder), so it needs editing for anyone else
  • Does not address branches, pull requests or code review
  • Relies on an external `git-commit` skill for message conventions and on docs/SETUP.md for GitHub setup
When to use it

Use it when a beginner user wants to back up finished work to GitHub and needs a safe, guided commit-and-push sequence.

When not to use it

Skip it for shared repositories that need branching, rebasing or pull requests, or on non-Python projects without adapting the test command.

Security analysis

Safe
Quality score88/100

This is a straightforward git workflow guide. It only runs ordinary developer commands (git status/add/commit/push, uv run pytest) for the legitimate purpose of committing and backing up work. It contains explicit safety guardrails: it forbids committing .env files, data/, API keys or personal details, forbids `git add .`, forbids force pushing, and tells the agent to stop and ask the user on conflicts or test failures. No destructive operations, no network exfiltration, no obfuscation, and no attempt to override agent instructions.

No concerns found

How this analysis is made

Examples

Save after a change
I just added Laguna Beach to my cities list — save my work.
Back up to GitHub
Back up my changes to GitHub please.
Commit and push
Commit and push everything I changed today.

name: save-work description: Save Steve's code changes to GitHub (git commit + push) in a safe, beginner-friendly way. Use when Steve says save, back up, commit, push, or after finishing a change.

Save work to GitHub

Here "saving" means two things. A commit is a labelled save point on this computer. A push copies that save point to GitHub as a backup.

  1. Run git status. If nothing changed, tell Steve "Nothing new to save" and stop.
  2. Safety check: never save .env, anything in data/, or any file that holds an API key or an owner's personal details. If you see one, stop and tell Steve.
  3. Run the tests: uv run pytest. If they fail, fix the problem first, or ask Steve whether to save anyway.
  4. Add the changed files by name: git add <file> <file>. Never use git add ..
  5. Commit with a short, clear message, as the git-commit skill describes. For example: git commit -m "feat: add Laguna Beach to my cities".
  6. Push: git push. If it fails because GitHub has newer changes, run git pull --no-rebase, then git push again. If there is a conflict, stop and explain it to Steve simply. Never force push.
  7. Tell Steve in one line what you saved. For example: "Saved and backed up: added Laguna Beach to your cities."

If the project has no GitHub copy of its own yet (git remote -v shows no origin), only commit. Then offer the GitHub step in docs/SETUP.md.

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 files

This 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.md

From the root of a test project, save the file as .skill-downloads/save-work-to-github-mvda870w/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/save-work-to-github-mvda870w' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/save-work-to-github-mvda870w/download' --output '.skill-downloads/save-work-to-github-mvda870w/SKILL.md.part' && mv '.skill-downloads/save-work-to-github-mvda870w/SKILL.md.part' '.skill-downloads/save-work-to-github-mvda870w/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

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/save-work-to-github-mvda870w/SKILL.md' && test -s '.skill-downloads/save-work-to-github-mvda870w/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/save-work' && cp -R '.skill-downloads/save-work-to-github-mvda870w' '.claude/skills/save-work'

Cursor
test -f '.skill-downloads/save-work-to-github-mvda870w/SKILL.md' && test -s '.skill-downloads/save-work-to-github-mvda870w/SKILL.md' && mkdir -p '.cursor/skills' && test ! -e '.cursor/skills/save-work' && cp -R '.skill-downloads/save-work-to-github-mvda870w' '.cursor/skills/save-work'

Codex
test -f '.skill-downloads/save-work-to-github-mvda870w/SKILL.md' && test -s '.skill-downloads/save-work-to-github-mvda870w/SKILL.md' && mkdir -p '.agents/skills' && test ! -e '.agents/skills/save-work' && cp -R '.skill-downloads/save-work-to-github-mvda870w' '.agents/skills/save-work'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/save-work-to-github-mvda870w'

openskills read 'save-work-to-github-mvda870w'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

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/save-work-to-github-mvda870w/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.

Related skills

React Hook Form Best Practices

Development

Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.

Claude CodeCursorWindsurf+2intermediateSafe 108,623
Skills Guide Bot

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.

Claude CodeCursorWindsurf+1intermediateSafe 48,981
Skills Guide Bot

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.

Claude CodeCursorCodexintermediateSafe 135,015
Skills Guide Bot