Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

git-save

Sterne11

Forks0

Aktualisiert26. Juni 2026 um 00:52

Stage and commit code changes with Conventional Commits format. Use when: code changes are complete and ready to commit, after review approval, user says 'save', 'commit', 'ship it'. Don't use when: tests are failing or work is still in progress.

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

In Manus ausführen

Quelle

brolag

brolag/neural-claude-code

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

In Manus ausführen

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

SoftwareentwicklerInformatik- und Mathematikberufe·SOC 15-1252

SKILL.md

readonly

Mehr aus diesem Repository

gleiches Repository

html

brolag/neural-claude-code

Render a Claude Code plan (PlanViewer), a task result, or a recap of a branch/commit/PR diff (ResultViewer) as a single-file HTML artifact with anti-fatigue UX. Use when the user asks for an HTML artifact, a plan/result/recap view, or to "show this as HTML". Not for plain markdown/text or one-liners.

2026-07-0111

craft

brolag/neural-claude-code

Build a planned change: take an approved /spec plan, capture a baseline, execute the subtasks, review with /vet and /exercise in a clean context, measure the delta, and stop for ship. If no approved plan exists, runs /spec first. Don't use for trivial changes (<25 LOC); edit directly.

2026-06-2611

exercise

brolag/neural-claude-code

Behavioral verification gate: run the test suite, then drive the running software as a real user (CLI/HTTP by default; browser or computer-use if those MCP tools are available) to confirm a feature works end to end. Reports PASS/FAIL per scenario with evidence. Use after a build, before ship, or as /craft's behavioral gate alongside /vet. Don't use for static code review (that is /vet).

2026-06-2611

slop-scan

brolag/neural-claude-code

Scan a codebase for accumulated slop, technical debt, dead code, and refactor opportunities. Use when user says 'scan for slop', 'find tech debt', 'what needs cleanup', or before a refactor sprint.

2026-06-2611

spec

brolag/neural-claude-code

Plan a non-trivial change BEFORE any code: research the context, decompose into testable subtasks, lock signatures, note CWE invariants, write executable acceptance, and surface contradictions. Produces an approvable plan artifact and STOPS for review. Does not write code. Pairs with /craft, which executes the plan. Don't use for trivial changes (<25 LOC) or pure conversation.

2026-06-2611

vet

brolag/neural-claude-code

Clean-context review gate. An independent reviewer (a fresh Agent, with no author context) challenges the diff for correctness, verifies it meets the approved spec's acceptance criteria, and checks project consistency. Verdict SHIP/HOLD/BLOCK. Use standalone before a PR/merge, or as craft's review phase. Don't use for trivial changes (<15 LOC) or docs-only edits.

2026-06-2611

name	git-save
description	Stage and commit code changes with Conventional Commits format. Use when: code changes are complete and ready to commit, after review approval, user says 'save', 'commit', 'ship it'. Don't use when: tests are failing or work is still in progress.
trigger	commit, save, ship it, git save
disable-model-invocation	true
allowed-tools	Bash(git status ), Bash(git diff ), Bash(git log ), Bash(git add ), Bash(git commit *)

/git-save — Commit Workflow

git status — identify changed files
git diff — understand what changed
git log --oneline -5 — match existing commit style
Stage specific files by name (never git add -A)
Skip files that look sensitive (.env, credentials, keys)
Draft commit: type(scope): description

Commit Types

type	when
`feat`	new feature
`fix`	bug fix
`refactor`	restructure, no behavior change
`docs`	documentation only
`test`	tests added/updated
`chore`	build, deps, config

Rules

NEVER commit if tests are failing
NEVER commit .env or credential files
NEVER auto-push (commit only, user pushes manually)
Ask before committing if scope is unclear