Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

git-staged

Estrelas2

Forks0

Atualizado13 de maio de 2026 às 02:58

Commit specific files without disturbing the existing git index. Use when the user wants to commit only certain files while preserving other already-staged changes, or when managing complex staging scenarios where the index must be carefully maintained across commits.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

cyberfly

cyberfly/agent-skills

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Desenvolvedores de softwareInformática e Matemática·SOC 15-1252

SKILL.md

readonly

name	git-staged
description	Commit specific files without disturbing the existing git index. Use when the user wants to commit only certain files while preserving other already-staged changes, or when managing complex staging scenarios where the index must be carefully maintained across commits.

git-staged

Commit specific files without disturbing already-staged changes in the git index.

Quick start

# 1. Save currently staged files
git diff --cached --name-only > /tmp/.git_staged_save

# 2. Clear the index (working tree untouched)
git reset HEAD

# 3. Stage and commit only the target files
git add <target-files>
git commit -m "your message"

# 4. Restore the previously staged files
xargs git add < /tmp/.git_staged_save

Workflows

Commit specific files, preserve existing index

Record currently staged files

git diff --cached --name-only > /tmp/.git_staged_save

Clear the index
```
git reset HEAD
```
Working tree is untouched — only the index is cleared.

Stage and commit target files

git add <file1> <file2>
git commit -m "message"

Restore previously staged files
```
xargs git add < /tmp/.git_staged_save
```
Files that were just committed will be re-staged with no net change if unmodified.

Use git stash when hunks are involved

When staged changes include partial hunks (git add -p), the file-list approach loses hunk precision. Use stash instead:

git stash push --staged -m "save-index"

git add <target-files>
git commit -m "message"

```
git stash pop
```
Resolve conflicts if committed files overlap with stashed changes.

Scenario guide

Situation	Approach
Staged files have no working-tree changes	Save/restore file list (Quick start)
Staged changes include partial hunks	`git stash push --staged`
Splitting one large staged change into multiple commits	Repeat stash workflow per commit

Notes

git reset HEAD never modifies the working tree — always safe.
If a previously-staged file has working-tree modifications, re-adding it will stage its current state — verify with git diff --cached before the next commit.
Clean up the temp file when done: rm /tmp/.git_staged_save

Mais deste repositório

mesmo repositório

staticbase

cyberfly/agent-skills

Scaffold a new static website project using the staticbase stack (Vite 7, Tailwind CSS 4, Alpine.js 3, markdown-powered blog). Use when user wants to create a new static site, website project, scaffold a staticbase project, or mentions the staticbase generator.

2026-07-022

playwright-save-test

cyberfly/agent-skills

Converts a Playwright MCP browser-automation session (e.g. trial-and-error form filling, login, or checkout) into a standalone, deterministic Playwright Test (.spec.ts) file that replays the same flow without AI. Use when the user asks to save/turn a Playwright MCP session into a test or script, wants to make a browser flow repeatable, or after a multi-step Playwright MCP task succeeds and re-running AI for the same flow next time would be wasteful.

2026-07-022

session-log

cyberfly/agent-skills

Records the decisions, tradeoffs, and rationale from the current session into a per-branch markdown log under docs/. Derives the filename from the git branch (slashes become hyphens) so one branch maps to one file, and appends a new timestamped section on every run — multiple sessions on the same branch accumulate in the same file. Use when the user invokes /session-log, or asks to document, log, or record the decisions, tradeoffs, or rationale made during a session.

2026-07-012

pr-description

cyberfly/agent-skills

Craft a GitHub pull request description in markdown from the changes on the current branch. Captures the task/goal, decisions and rationale, open questions, tests to run, and a preview section. Use when the user invokes /pr-description, asks to write or generate a PR description/body, or is opening a pull request and wants a summary of branch changes.

2026-06-092

staged

cyberfly/agent-skills

Stage only the files the agent modified in this session, then suggest a commit message (without committing). Use when the user invokes /staged or wants to git add only the agent's recent changes while leaving any manual edits unstaged.

2026-06-092

checkpoint

cyberfly/agent-skills

Save important conversation context to a timestamped handoff file in .claude/checkpoints/ so it can be loaded into a new session before context runs out. Captures current task, decisions and rationale, work completed, and open questions. Copies the full handoff to the clipboard via pbcopy. Use when the user invokes /checkpoint, says context is getting full, wants to hand off to a new session, or asks to save/snapshot session state for later.

2026-06-092

name	git-staged
description	Commit specific files without disturbing the existing git index. Use when the user wants to commit only certain files while preserving other already-staged changes, or when managing complex staging scenarios where the index must be carefully maintained across commits.

git-staged

Commit specific files without disturbing already-staged changes in the git index.

Quick start

# 1. Save currently staged files
git diff --cached --name-only > /tmp/.git_staged_save

# 2. Clear the index (working tree untouched)
git reset HEAD

# 3. Stage and commit only the target files
git add <target-files>
git commit -m "your message"

# 4. Restore the previously staged files
xargs git add < /tmp/.git_staged_save

Workflows

Commit specific files, preserve existing index

Record currently staged files

git diff --cached --name-only > /tmp/.git_staged_save

Clear the index
```
git reset HEAD
```
Working tree is untouched — only the index is cleared.

Stage and commit target files

git add <file1> <file2>
git commit -m "message"

Restore previously staged files
```
xargs git add < /tmp/.git_staged_save
```
Files that were just committed will be re-staged with no net change if unmodified.

Use git stash when hunks are involved

When staged changes include partial hunks (git add -p), the file-list approach loses hunk precision. Use stash instead:

git stash push --staged -m "save-index"

git add <target-files>
git commit -m "message"

```
git stash pop
```
Resolve conflicts if committed files overlap with stashed changes.

Scenario guide

Situation	Approach
Staged files have no working-tree changes	Save/restore file list (Quick start)
Staged changes include partial hunks	`git stash push --staged`
Splitting one large staged change into multiple commits	Repeat stash workflow per commit

Notes

git reset HEAD never modifies the working tree — always safe.
If a previously-staged file has working-tree modifications, re-adding it will stage its current state — verify with git diff --cached before the next commit.
Clean up the temp file when done: rm /tmp/.git_staged_save