Run any Skill in Manus with one click

staged

Stars2

Forks0

UpdatedJune 9, 2026 at 04:42

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.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

cyberfly

cyberfly/agent-skills

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	staged
description	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.

staged

Stage only the files you (the agent) modified this session — not everything in the working tree.

Workflow

Identify files touched this session Look back through your tool call history for all Edit, Write, and NotebookEdit calls. Collect the unique set of file paths you actually modified or created.
Cross-check against git status
```
git status --short
```
Only stage paths that appear in both your session history and the git working tree diff. Skip files you touched that are already clean (e.g. reverted).
Stage only those files
```
git add <file1> <file2> ...
```
Confirm what is now staged
```
git diff --cached --stat
```
Generate a commit message Inspect the staged diff and write a Conventional Commits message directly — do not invoke the commit-message skill (saves tokens).
```
git diff --cached          # full diff for context
```
Format: <type>(<scope>): <subject> with an optional body after a blank line.
- type: feat (new capability), fix (bug), chore (deps/config/tooling), docs, refactor (no behavior change), test, style (formatting), perf, build, ci, revert.
- scope (optional): short noun for the area changed (auth, api, ui, db). Omit when changes span many areas.
- subject: imperative mood ("add" not "added"), lowercase first letter, no trailing period, first line ≤ 72 chars.
- body (optional): add only when the why isn't obvious from the subject.
Present the message to the user — do not commit automatically unless they ask.

Report the list of staged files alongside the suggested commit message.

Edge cases

You modified nothing this session — report that and stop.
A file you edited has no diff (change was reverted) — skip it.
User says "not all of them" — list your session files and ask which ones to include before staging.
Untracked files you created — include them; call them out so the user can .gitignore any that are sensitive.

Notes

Never commit — this skill stops at staging.
Never use git add -A or git add . — that would include manual user changes outside this session.

More from this repository

same repository

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

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

load-checkpoint

cyberfly/agent-skills

Load a saved checkpoint from .claude/checkpoints/ to restore important context from a previous session. Defaults to the most recent file; lets the user pick if they want a different one. Use when the user invokes /load-checkpoint, starts a new session referencing previous work, says "resume where we left off", or wants to pick up from a handoff written by /checkpoint.

2026-06-092

name	staged
description	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.

staged

Stage only the files you (the agent) modified this session — not everything in the working tree.

Workflow

Identify files touched this session Look back through your tool call history for all Edit, Write, and NotebookEdit calls. Collect the unique set of file paths you actually modified or created.
Cross-check against git status
```
git status --short
```
Only stage paths that appear in both your session history and the git working tree diff. Skip files you touched that are already clean (e.g. reverted).
Stage only those files
```
git add <file1> <file2> ...
```
Confirm what is now staged
```
git diff --cached --stat
```
Generate a commit message Inspect the staged diff and write a Conventional Commits message directly — do not invoke the commit-message skill (saves tokens).
```
git diff --cached          # full diff for context
```
Format: <type>(<scope>): <subject> with an optional body after a blank line.
- type: feat (new capability), fix (bug), chore (deps/config/tooling), docs, refactor (no behavior change), test, style (formatting), perf, build, ci, revert.
- scope (optional): short noun for the area changed (auth, api, ui, db). Omit when changes span many areas.
- subject: imperative mood ("add" not "added"), lowercase first letter, no trailing period, first line ≤ 72 chars.
- body (optional): add only when the why isn't obvious from the subject.
Present the message to the user — do not commit automatically unless they ask.

Report the list of staged files alongside the suggested commit message.

Edge cases

You modified nothing this session — report that and stop.
A file you edited has no diff (change was reverted) — skip it.
User says "not all of them" — list your session files and ask which ones to include before staging.
Untracked files you created — include them; call them out so the user can .gitignore any that are sensitive.

Notes

Never commit — this skill stops at staging.
Never use git add -A or git add . — that would include manual user changes outside this session.