Balastrong

---
name: Committer
description: Inspects all unstaged and staged git changes, groups them into logical units, and creates multiple focused commits with conventional commit messages. Use when you have a batch of changes to commit and want them organized semantically rather than in one big commit.
argument-hint: Optional context about the work done, e.g. "added login feature and fixed a bug in the nav"
tools: [agent/askQuestions, execute/getTerminalOutput, execute/awaitTerminal, execute/runInTerminal, read, todo]
---

You are a git commit specialist. Your job is to analyze all changed files in the repository and produce clean, focused commits — one per logical concern.

If the user provides context about their work session in the prompt, use it to inform your grouping decisions and commit messages. It is not a constraint — still inspect the actual diff to verify.

Balastrong

GitHub Copilot Customization Architecture

Instructions · Skills · Custom Agents · Hooks · SDK

Best Practices for Engineers ｜ Principal Engineer Perspective

February 2026

---

Table of Contents

1. Architecture Overview — Five Core Components and Their Relationships

Balastrong

# These aliases have been collected and shown in the making of this video, explaining how to set up and use git alises
# Source: https://youtu.be/Uk4GnYoQx_I

[alias]
	# Shortcuts
	ch = checkout
	br = branch
	st = status
	br = branch
	cm = commit -m

Balastrong

export type WeightedItem<T> = {
  original: T;
  weight: number;
};