Files

Balogh István Barnabás 3d9d01d05b Add graphify references for various export and processing steps

- Create exports.md for additional export options and benchmarks in graphify.
- Add extraction-spec.md detailing the extraction subagent prompt and rules.
- Introduce github-and-merge.md for instructions on cloning GitHub repositories and merging graphs.
- Implement hooks.md for setting up commit hooks and CLAUDE.md integration.
- Develop query.md for querying the graph, including pathfinding and explanation features.
- Add transcribe.md for transcribing video and audio files into text.
- Create update.md for incremental updates and handling cluster-only operations.
- Add resolve-comments.md snippet for resolving comments in code changes.

2026-07-18 14:42:25 +02:00

2.0 KiB

Raw Blame History

description, agent

description	agent
Create git commit with auto-generated conventional commit message	build

Git Commit Command

Create a well-structured git commit by analyzing staged changes and generating a conventional commit message.

Phase 1: Gather Context

Run these commands in parallel to understand the current state:

git status - See all staged and unstaged changes
git diff --cached - View the actual staged changes that will be committed
git log --oneline -5 - Review recent commit message style for consistency

Phase 2: Analyze Changes

Based on the staged diff, determine:

Change Type (use conventional commits):
- feat: New feature
- fix: Bug fix
- refactor: Code restructuring without behavior change
- docs: Documentation only
- test: Adding or updating tests
- chore: Maintenance tasks
- style: Formatting, whitespace
- perf: Performance improvement
- ci: CI/CD changes
Scope (optional): Affected module or component
Description: Concise summary focusing on WHY, not WHAT

Phase 3: Generate Commit Message

Format: type(scope): description

Rules:

Use imperative mood ("Add feature" not "Added feature")
Keep first line under 72 characters
Focus on the purpose and impact
Add body for complex changes explaining reasoning

Phase 4: Execute Commit

If there are unstaged changes that should be included, ask user first
Stage any additional files if requested
Execute the commit with the generated message
Run git status to verify success

Output Format

Commit Analysis
---------------
Type: [type]
Scope: [scope or "none"]
Files: [number] files changed

Generated Message:
[commit message]

Commit Status: [success/failure]

Safety Checks

NEVER commit files that appear to contain secrets (.env, credentials, API keys)
WARN if committing lock files or large binary files
CONFIRM before committing if there are untracked files that might be forgotten

2.0 KiB Raw Blame History