ワンクリックでManusで任意のスキルを実行

git-agent-session-start

スター1

フォーク0

更新日2026年4月5日 20:04

Use this skill when you need to start an agent session in a Git repository by inspecting branch, remote, worktree, and risk signals before any modification.

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

niboj

niboj/agent-skills-git

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

Purpose

Establish a safe Git baseline before the agent changes anything.

When To Use

before the first write action in a repository
when a user asks the agent to inspect or modify a repo
when the repository state is unknown

When Not To Use

when the task is purely conceptual and does not touch a repository
after another Git skill already produced a fresh repository-state summary in the same session

Required Inputs

repository path
intended task
known branch policy, if any

Ordered Procedure

Run git status --short --branch, git branch --show-current, and git remote -v.
Check for detached HEAD, untracked files, unstaged changes, staged changes, missing remotes, or in-progress merge/rebase state.
Summarize the current state in plain language.
If the state is unsafe or ambiguous, stop and route to git-agent-refuse-unsafe-state or another specialized skill.
If the state is safe, state the branch, cleanliness, remote posture, and next safe Git step.

Guardrails

never assume main is safe for direct commits
refuse checkout, pull, reset, clean, or rebase before inspection
call out missing or suspicious remotes explicitly

Output Expectations

current branch
concise worktree summary
remote summary
explicit go or stop decision with reason

Examples

EX-001. Start an agent session in a clean repository

Context: a user asks the agent to update documentation in a repository with no visible pending work.
Objective: confirm that the repository is safe for a new task.
Preconditions: git status --short --branch reports a clean worktree on feature/142-docs-refresh; origin is configured.
Actions: run the three inspection commands; confirm there is no merge, rebase, or detached HEAD; report the branch and cleanliness; proceed to the requested task.
Expected result: the agent states that the repository is clean, the branch is known, and work may continue safely.
Guardrails: still warn if the current branch is protected or unexpected for the requested task.
Concerned skill: git-agent-session-start

EX-004. Start an agent session in detached HEAD state

Context: the user asks for a quick patch, but the repository is checked out at a raw commit.
Objective: detect the detached HEAD before any commit-producing action.
Preconditions: git branch --show-current is empty and git status --short --branch shows ## HEAD (no branch).
Actions: inspect branch and remotes; explain that any commit would be difficult to trace; ask whether to create or switch to a proper branch first.
Expected result: the agent refuses to continue with normal branch-based work until the branch situation is clarified.
Guardrails: do not create commits from detached HEAD without explicit confirmation and branch intent.
Concerned skill: git-agent-session-start

Related References

references/concepts.md
references/decision-rules.md
references/examples.md
assets/examples/sample-scenarios.md

このリポジトリの他の Skills

同じリポジトリ

git-agent-change-delivery

niboj/agent-skills-git

Use this skill when you need to deliver a complete Git change from inspected repository state through commit, push, and final human-facing summary.

2026-04-051

git-agent-refuse-unsafe-state

niboj/agent-skills-git

Use this skill when the Git repository is in an unsafe or ambiguous state and the agent must stop, explain the risk, and route to the safest next action.

2026-04-051

git-branch-workflow

niboj/agent-skills-git

Use this skill when you need to create, rename, or validate a Git work branch from a safe and synchronized base branch.

2026-04-051

git-commit-convention

niboj/agent-skills-git

Use this skill when you need to stage, split, and describe Git commits so each commit carries one clear intent with a traceable message.

2026-04-051

git-conflict-resolution-playbook

niboj/agent-skills-git

Use this skill when you need to resolve Git merge or rebase conflicts methodically, document the chosen resolution, and validate the repository before continuing.

2026-04-051

git-hotfix-workflow

niboj/agent-skills-git

Use this skill when you need to create, deliver, and document an urgent Git hotfix from the correct protected base without bypassing review and safety rules.

2026-04-051

Ordered Procedure

Run git status --short --branch, git branch --show-current, and git remote -v.

Check for detached HEAD, untracked files, unstaged changes, staged changes, missing remotes, or in-progress merge/rebase state.

Summarize the current state in plain language.

If the state is unsafe or ambiguous, stop and route to git-agent-refuse-unsafe-state or another specialized skill.

If the state is safe, state the branch, cleanliness, remote posture, and next safe Git step.

Examples

EX-001. Start an agent session in a clean repository

Context: a user asks the agent to update documentation in a repository with no visible pending work.

Objective: confirm that the repository is safe for a new task.

Preconditions: git status --short --branch reports a clean worktree on feature/142-docs-refresh; origin is configured.

Actions: run the three inspection commands; confirm there is no merge, rebase, or detached HEAD; report the branch and cleanliness; proceed to the requested task.

Expected result: the agent states that the repository is clean, the branch is known, and work may continue safely.

Guardrails: still warn if the current branch is protected or unexpected for the requested task.

Concerned skill: git-agent-session-start

EX-004. Start an agent session in detached HEAD state

Context: the user asks for a quick patch, but the repository is checked out at a raw commit.

Objective: detect the detached HEAD before any commit-producing action.

Preconditions: git branch --show-current is empty and git status --short --branch shows ## HEAD (no branch).

Actions: inspect branch and remotes; explain that any commit would be difficult to trace; ask whether to create or switch to a proper branch first.

Expected result: the agent refuses to continue with normal branch-based work until the branch situation is clarified.

Guardrails: do not create commits from detached HEAD without explicit confirmation and branch intent.

Concerned skill: git-agent-session-start

name	git-agent-session-start
description	Use this skill when you need to start an agent session in a Git repository by inspecting branch, remote, worktree, and risk signals before any modification.