Skip to content

rse/ase / plugin/skills/ase-repo-stage

ase-repo-stage

Verified

Stage only the part of the current Git working copy changes which belongs to a topic, to the last `CHANGELOG.md` entry, to the last turn, or to the entire session, by picking and, if necessary, splitting hunks, check that the staged state builds on its own, and optionally chain into ChangeLog updating and commit message crafting. Use when the user calls to "stage" only a part of the changes, like "the hunks related to" a topic or "the last turn".

FileKindSize
SKILL.mdskill md19.7 KB
help.mdmarkdown4.3 KB

##  NAME

`ase-repo-stage` - Stage a Part of the Changes

##  SYNOPSIS

`ase-repo-stage`
    [`--help`|`-h`]
    [`--entry`|`-e`]
    [`--turn`|`-t`]
    [`--session`|`-s`]
    [`--merge`|`-m`]
    [`--no-verify`|`-V`]
    [`--worktree`|`-w`]
    [`--changelog`|`-c`]
    [`--commit`|`-C`]
    [*topic*]

##  DESCRIPTION

The `ase-repo-stage` skill stages only the *part* of the current Git working copy changes which
belongs to a *selection*, so a mixed change set can be committed in cohesive portions without
hand-crafted partial patches.

The selection is either a free-text *topic*, the *last* `CHANGELOG.md` entry (`--entry`), the
changes of the *last turn* (`--turn`), or all changes of the current *session* (`--session`).
Without an option, the selection is inferred from the *topic* text, so `stage the last turn`
works, too. An explicitly given option overrides the inference, and a remaining *topic* narrows
the entry, turn, and session selections.

The changes are picked at the granularity of individual *lines*: hunks which belong to the
selection only partially are *split*, and untracked files are selectable, even partially.
Mutually dependent changes, like a use and its import, are kept together. Unless `--merge` is
given, the selection *replaces* the current index content, which is refused if a file has both
staged and unstaged changes. Only the Git index is changed, never the content of a working copy
file.

After staging, the skill checks that the *staged state alone builds*, with the build command
auto-detected from the project. By default, the remaining unstaged changes are temporarily
stashed for this, or -- under `--worktree` -- the staged state is built in a temporary worktree.
A failed build keeps the staged selection and is reported with its essential error lines.

Finally, the skill optionally chains into the ChangeLog updating and the commit message
crafting, both for the staged selection, unless the build check failed.

##  OPTIONS

-   `--entry`|`-e`:
    Select the changes which realize the *last* `CHANGELOG.md` entry, i.e. the entry added or
    modified by the uncommitted change of `CHANGELOG.md`, plus the entry itself.

-   `--turn`|`-t`:
    Select the changes made by the agent in the *last turn* before the skill invocation.

-   `--session`|`-s`:
    Select all changes made by the agent in the current *session*.

-   `--merge`|`-m`:
    Stage the selection *on top* of the already staged changes, instead of replacing them.

-   `--no-verify`|`-V`:
    Skip the check that the staged state builds on its own.

-   `--worktree`|`-w`:
    Check the build in a *temporary Git worktree* holding only the staged state, instead of
    temporarily stashing the unstaged changes of the working copy.

-   `--changelog`|`-c`:
    Afterwards, update the `CHANGELOG.md` entries via `ase-repo-changelog` and stage exactly the
    entries it added or updated.

-   `--commit`|`-C`:
    Afterwards, craft the commit message of the staged selection via `ase-repo-commit`.

The options `--entry`, `--turn`, and `--session` are mutually exclusive.

##  ARGUMENTS

-   *topic*:
    A free-text description of the changes to stage, or -- without an option -- a reference
    like `last turn` or `last changelog entry` the selection is inferred from.

##  SCENARIOS

-   You want only the hunks related to a certain topic staged
-   You want only the changes of the last turn or of the session staged
-   You want the changes behind a `CHANGELOG.md` entry staged and committed
-   You want to be sure the staged part builds without the rest of the changes

##  EXAMPLES

Stage only the hunks related to a topic:

```text
❯ /ase-repo-stage the getopt negation handling
```

Stage the changes of the last turn, checking the build in a temporary worktree:

```text
❯ /ase-repo-stage --turn --worktree
```

Stage the changes of the last ChangeLog entry and craft its commit message:

```text
❯ /ase-repo-stage --entry --commit
```

Add the session changes related to a topic to the already staged ones:

```text
❯ /ase-repo-stage --session --merge task board
```

##  SEE ALSO

[`ase-repo-dissect`](../ase-repo-dissect/help.md), [`ase-repo-diff`](../ase-repo-diff/help.md),
[`ase-repo-review`](../ase-repo-review/help.md), [`ase-repo-commit`](../ase-repo-commit/help.md),
[`ase-repo-changelog`](../ase-repo-changelog/help.md).
rea-changelog-updatemorluto/reaPrepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
academy-guideanthropics/skillsStop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
claude-apianthropics/skillsReference for the Claude API / Anthropic SDK — model ids, pricing, params, streaming, tool use, MCP, agents, caching, token counting, model migration. TRIGGER — read BEFORE opening the target file; don't skip because it "looks like a one-liner" — whenever: the prompt names Claude/Anthropic in any form (Claude, Anthropic, Fable, Opus, Sonnet, Haiku, `anthropic`, `@anthropic-ai`, `claude-*`, `us.anthropic.*`, `[1m]`); the user asks about an LLM (pricing/model choice/limits/caching) — never answer from memory; OR the task is LLM-shaped with provider unstated (agent/MCP/tool-definition/multi-agent/RAG/LLM-judge/computer-use; generate/summarize/extract/classify/rewrite/converse over NL; debugging refusals/cutoffs/streaming/tool-calls/tokens). SKIP only when another provider is being worked on (overrides all triggers): OpenAI/GPT/Gemini/Llama/Mistral/Cohere/Ollama named in the query; OR `grep -rE 'openai|langchain_openai|google.generativeai|genai|mistralai|cohere|ollama'` over the project hits (run this grep FIRST if no provider named — don't Read the file).Stars: 198kUpdated Claude CodeCodexUnverifiedInstall
doc-coauthoringanthropics/skillsGuide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.Stars: 198kUpdated Claude CodeCodexVerifiedInstall