git master

Engineering Community

Skill notes

MODE DETECTION (FIRST STEP)

Analyze the user's request to determine operation mode: User Request Pattern · Mode · Jump To "commit", "커밋", changes to commit · COMMIT · Phase 0-6 (existing) "rebase", "리베이스", "squash", "cleanup history" · REBASE · Phase R1-R4 "find when", "who changed", "언제 바뀌었", "git blame", "bisect" · HISTORY_SEARCH · Phase H1-H3

CORE PRINCIPLE: MULTIPLE COMMITS BY DEFAULT (NON-NEGOTIABLE)

<critical_warning> ONE COMMIT = AUTOMATIC FAILURE Your DEFAULT behavior is to CREATE MULTIPLE COMMITS. Single commit is a BUG in your logic, not a feature. HARD RULE:

PHASE 0: Parallel Context Gathering (MANDATORY FIRST STEP)

<parallel_analysis> Execute ALL of the following commands IN PARALLEL to minimize latency: Capture these data points simultaneously: What files changed (staged vs unstaged) Recent 30 commit messages for style detection

PHASE 1: Style Detection (BLOCKING - MUST OUTPUT BEFORE PROCEEDING)

<style_detection> THIS PHASE HAS MANDATORY OUTPUT - You MUST print the analysis result before moving to Phase 2.

1.2 Commit Style Classification

Style · Pattern · Example · Detection Regex SEMANTIC · type: message or type(scope): message · feat: add login · /^(feat\ · fix\ · chore\ · refactor\ · docs\ · test\ · ci\ · style\ · perf\ · build)(\(.+\))?:/ PLAIN · Just description, no prefix · Add login feature · No conventional prefix, >3 words SENTENCE · Full sentence style · Implemented the new login flow · Complete grammatical sentence

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Engineering
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@code-yeongyu · no license declared
Token usage
Heavy
Setup complexity
Guided setup
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
Network behavior
External requests
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

Output preview git-master.preview
# PHASE 1: Style Detection (BLOCKING - MUST OUTPUT BEFORE PROCEEDING)

<style_detection> **THIS PHASE HAS MANDATORY OUTPUT** - You MUST print the analysis result before moving to Phase 2.

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.