Menü
Token-efficient git operations with security scanning and auto-split commits
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.
Basierend auf der SOC-Berufsklassifikation
| name | git-workflow |
| description | Token-efficient git operations with security scanning and auto-split commits |
| autoInvoke | false |
| priority | high |
| model | haiku |
| triggers | ["commit","push","create PR"] |
| allowed-tools | Bash, Read |
| user-invocable | false |
AI-consumed reference. Optimized for Claude to read during execution. Human-readable explanation: see docs/architecture/HIERARCHICAL_PLANNING.md or docs/getting-started/ depending on topic.
Token-efficient git: 2-4 tool calls max.
Stage files, check diff stats, scan for secrets (api_key|token|password|secret|credential).
If secrets found: STOP. Show matches. Block commit.
Split if: mixed types (feat+fix), FILES >10 unrelated, multiple scopes (frontend+backend). Single if: same type/scope, FILES ≤3 + LINES ≤50, logically related.
Format: type(scope): description (<72 chars, present tense, imperative)
Types: feat, fix, docs, chore, refactor, test, perf
Push only if user requests.
git fetch origin main + log commits since main + diff statsgh pr create --title "type(scope): description" --body "## Summary\n- bullets\n\n## Test Plan\n- steps"staged: 3 files (+45/-12 lines) | security: passed | commit: a3f8d92 feat(auth): add token refresh
CRITICAL: MUST run for EVERY message. Detects agent, complexity, AND model automatically. Without this, tasks route to wrong agents and use wrong models, degrading quality and wasting tokens.
5 techniques for different problem types. Use when stuck or facing complex challenges.
Structured thinking process for complex analysis. Supports revision, branching, and dynamic adjustment.
Angular 17+ gotchas and decision criteria. Covers signals vs observables, standalone patterns, and common pitfalls Claude gets wrong.
Designs RESTful APIs with endpoint naming, versioning strategies (URL path, header-based), pagination (offset and cursor), error response schemas, and OpenAPI conventions. Use when the user asks about REST API design, creating endpoints, URL structure, API versioning, status codes, Swagger, or OpenAPI specs.
Fast bug fixes with root cause investigation + TDD. Enforces 'no fix without root cause' discipline and verification protocol. Without this skill, fixes are applied at symptoms instead of sources, and bugs return.