Ir para o conteúdo principal
Developer

Git Cheatsheet

Interactive visual reference for essential Git commands.

0 of 3 uses today · 3 remaining. Go Pro and remove the limit.

Upgrade

Git Cheatsheet

Git cheatsheetReal scenariosOn-device processing

Navigate by objective, recover safely, and scale without memorizing everything in Git.

Track
3 scenarios
Commands
17
Caution
0 high
Recovery
Assisted
01

Filter by scenario

Search track
Presets

Start repository

Create repo, prepare base branch, and connect remote without friction.
basic
git initlow
Initializes the repository in the current folder.
git add .low
Moves initial files to staging.
git commit -m "chore: init"low
Creates the first baseline commit.
git branch -M mainlow
Standardizes the main branch before push.
git remote add origin <url>low
Connects the main remote repository.
git remote add origin https://github.com/org/repo.git
git push -u origin mainlow
Publishes the base branch and sets upstream.

Feature flow

Open working branch, update base, and integrate back with clarity.
basic
git switch -c feature/<tema>low
Creates and switches to the feature branch.
git switch -c feature/login
git add .low
Updates staging with current progress.
git commit -m "feat: ..."low
Records a work step with context.
git fetch originlow
Updates remote references before integration.
git switch mainlow
Returns to the integration base.
git merge feature/<tema>medium
Integrates the feature branch into the base.

Safe undo

Choose between restore, reset, and revert without accidentally destroying work.
basic
git restore <arquivo>medium
Discards uncommitted local change in a file.
git restore src/app/page.tsx
git restore --staged <arquivo>low
Removes file from staging without losing local edit.
git reset --soft HEAD~1medium
Goes back one commit keeping everything in staging.
git reset --mixed HEAD~1medium
Goes back one commit and returns changes to working tree.
git revert <hash>low
Creates a safe inverse commit for shared history.
02

Quick decision

Undo
Use restore for local files, revert for shared history, and reflog before aggressive reset.
Integration
Prefer merge when you want to preserve branching and rebase when you want to linearize before final merge.
Scale
Use worktree for parallel branches and sparse-checkout when the monorepo is too large for the current task.
03

Export

Recovery and selective delivery
Rebase with exit route, reflog for rescue, and cherry-pick for hotfix or backport without full merge.
Exportable runbook
Export the filtered track to CSV for technical inventory or TXT for shareable squad playbook.
04

Operational view

Clean
Low
13
Medium
4
High
0
Placeholders like <tema>, <arquivo>, <hash>, and <url> must be replaced before execution.
Sobre

What is Git Cheatsheet?

Por Quorify EditorialAtualizado em

Quorify's Git Cheatsheet tool is an interactive visual guide with essential commands for Git version control. Processing occurs locally in the browser via native APIs—useful when you need to handle sensitive data (tokens, secrets, production payloads) and prefer not to paste into online tools that send to external servers. Follows industry-recognized standards (IETF RFCs, W3C, MDN). Part of the Quorify dev toolkit—combine with other validation, conversion, and formatting tools to accelerate debugging, API integration, and project setup. Processing occurs locally, with no payload upload to external server at this stage. For details about data handling see our Privacy Policy.

Casos

When to use

  1. Quick debugging during API integration, without needing to open Postman or CLI tool.

  2. Validate payload before submitting to production, avoiding 400 error with generic message.

  3. Initial project setup—generate identifiers, format configuration, validate syntax.

  4. Review production log data, visually identifying patterns and errors.

  5. Technical customer support—validate received input before creating ticket for product team.

Método

How it works

Git Cheatsheet uses native browser APIs (Web Crypto, JSON, URL, TextEncoder) that implement recognized official standards (IETF RFCs, FIPS, ECMA). No heavy library or external server dependency. For full details about data handling see our Privacy Policy.

FAQ

Frequently asked questions

Does processing involve an external server?
No. Git Cheatsheet uses native browser APIs. Entered payloads are processed locally.
Can I use it with sensitive data (tokens, secrets)?
Yes, because processing is local. Still, avoid pasting real credentials into any web tool—always use staging environments or dummy variables for testing.
What standard is followed?
As applicable: IETF RFCs (JSON, UUID, URI), W3C (HTML, CSS), FIPS (cryptography), ECMA (JavaScript). See the Sources section for specific references.
Does it work offline?
After loading the page once, you can continue using the tool offline.
Is there a size limit?
Browsers support payloads in the hundreds of MB range in memory, but web tools typically slow down above ~10 MB. For large files use specialized CLI tools.
Is it compatible with older browser versions?
We recommend using current versions (Chrome, Firefox, Safari, Edge from the last 2 years). Modern features (Web Crypto, etc.) may not be available in old browsers.
Fontes

Official sources

Tabelas, leis e referências consultadas para fundamentar esta ferramenta.

  1. Technical documentationCurrentMDN Web Docs · Mozilla

    Web Standards

    The world's most consulted reference for web standards—JavaScript APIs, HTML, CSS, and browser protocols.

  2. International standardCurrentWorld Wide Web Consortium (W3C)

    W3C Standards

    Organization that defines official web standards—HTML, CSS, ARIA, and other specifications implemented by all browsers.

  3. International standardsDatatrackerIETF · Internet Engineering Task Force

    RFC Documents

    Official repository of Request for Comments (RFCs)—technical documents defining internet protocols and formats (HTTP, JSON, URI, UUID, etc).

Metodologia — esta ferramenta consulta as tabelas e legislação vigentes nas fontes acima. As regras são atualizadas conforme novas instruções normativas são publicadas pelos órgãos competentes.

Última verificação editorial: junho de 2026.

Compartilhe

Related

Related tools

toolLayout.related_description