تشغيل أي مهارة في Manus بنقرة واحدة

git-ops

النجوم٦

التفرعات٦

آخر تحديث٤ مايو ٢٠٢٦ في ٠٢:١٨

Git operations: status, diff, log, branch, add, commit following conventional commit format. Safety-first: destructive ops require explicit confirmation.

التثبيت

التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.

تشغيل في Manus

المصدر

juanmanueldaza

juanmanueldaza/fu7ur3pr00f

فتح مستودع GitHub عرض مستودعات المنشئ

تنزيل

تشغيل في Manus

المهن ذات الصلةSOC

استنادا إلى تصنيف SOC المهني

مطوّرو البرمجياتمهن الحاسوب والرياضيات·SOC 15-1252

SKILL.md

readonly

name	git-ops
description	Git operations: status, diff, log, branch, add, commit following conventional commit format. Safety-first: destructive ops require explicit confirmation.
compatibility	opencode

Skill: git-ops

When to Use

Use this skill when:

Checking repository state (git status, git log, git diff)
Creating commits following conventional commit format
Managing branches (create, switch, list, delete)
Staging changes (git add)
Any git operation that doesn't require remote access (that's github-ops territory)

Safety Rules

REQUIRE:

Run git status before any destructive operation
Never commit unless changes are explicitly staged by the user or calling agent
Reject git push --force to main/master unless the calling agent provides explicit rationale
Report to calling agent (do not proceed) if: dirty working tree blocks the operation, detached HEAD state, merge conflicts exist

REJECT if:

Working tree is dirty and the operation would lose uncommitted changes
The branch to be deleted has unmerged changes

Workflow: Creating a Commit

git status --short — show current state
git diff --stat — summary of changes
git diff — review full diff (pipe to calling agent for review)
git add <files> — stage specific files (never git add -A blindly)
Load the commits skill for conventional commit format rules
git commit -m "<type>(<scope>): <description>" — conform to conventional commits

Workflow: Branch Operations

git branch --list — list local branches
git checkout -b <name> — create and switch to new branch
git checkout <name> — switch to existing branch
Before deleting: verify branch is merged with git branch --merged

Workflow: Inspecting State

git status — working tree status
git log --oneline -n 20 — recent commits
git log --graph --oneline --all — branch graph
git diff — unstaged changes
git diff --staged — staged changes
git show <ref> — full details of a commit

Edge Cases

Empty repo (no commits): git rev-parse --verify HEAD fails. Handle by explaining this is a fresh repo and suggesting git add + first commit.
Detached HEAD: Warn calling agent before any commit or branch creation.
Large repos: Use git log --oneline -n 20 (limit output). Use -- <path> to scope diff/log to specific paths.
Merge conflicts: Report to calling agent with conflicting files. Do not attempt resolution.

المزيد من هذا المستودع

نفس المستودع

judgment-day

juanmanueldaza/fu7ur3pr00f

Dual-model adversarial review: local and delegated reviewers audit independently, verdicts are synthesized.

2026-05-316

sdd-apply

juanmanueldaza/fu7ur3pr00f

Implement the SDD task list. Read tasks and design from memory, write code, run tests.

2026-05-316

sdd-archive

juanmanueldaza/fu7ur3pr00f

Archive all SDD artifacts for a change as a single completed record in memory.

2026-05-316

sdd-design

juanmanueldaza/fu7ur3pr00f

Write the technical design for a planned change: components, interfaces, data flows, edge cases.

2026-05-316

sdd-explore

juanmanueldaza/fu7ur3pr00f

Explore the codebase to build context for a planned change. First phase of the SDD workflow.

2026-05-316

sdd-propose

juanmanueldaza/fu7ur3pr00f

Propose 2–3 solution approaches for a planned change, evaluating trade-offs and recommending one.

2026-05-316

Skill: git-ops

When to Use

Use this skill when:

Checking repository state (git status, git log, git diff)

Creating commits following conventional commit format

Managing branches (create, switch, list, delete)

Staging changes (git add)

Any git operation that doesn't require remote access (that's github-ops territory)

Safety Rules

REQUIRE:

Run git status before any destructive operation

Never commit unless changes are explicitly staged by the user or calling agent

Reject git push --force to main/master unless the calling agent provides explicit rationale

Report to calling agent (do not proceed) if: dirty working tree blocks the operation, detached HEAD state, merge conflicts exist

REJECT if:

Working tree is dirty and the operation would lose uncommitted changes

The branch to be deleted has unmerged changes

Workflow: Creating a Commit

git status --short — show current state

git diff --stat — summary of changes

git diff — review full diff (pipe to calling agent for review)

git add <files> — stage specific files (never git add -A blindly)

Load the commits skill for conventional commit format rules

git commit -m "<type>(<scope>): <description>" — conform to conventional commits

Workflow: Branch Operations

git branch --list — list local branches

git checkout -b <name> — create and switch to new branch

git checkout <name> — switch to existing branch

Before deleting: verify branch is merged with git branch --merged

Workflow: Inspecting State

git status — working tree status

git log --oneline -n 20 — recent commits

git log --graph --oneline --all — branch graph

git diff — unstaged changes

git diff --staged — staged changes

git show <ref> — full details of a commit

Edge Cases

Empty repo (no commits): git rev-parse --verify HEAD fails. Handle by explaining this is a fresh repo and suggesting git add + first commit.

Detached HEAD: Warn calling agent before any commit or branch creation.

Large repos: Use git log --oneline -n 20 (limit output). Use -- <path> to scope diff/log to specific paths.

Merge conflicts: Report to calling agent with conflicting files. Do not attempt resolution.