# Csharp Commit Todo Changes

> Stage and commit all changes accumulated across a completed TODO pipeline run with a clear, concise commit message

- Skill: `andybakerbrfc/csharp-commit-todo-changes` (Agent Skill)
- Install (CLI): `npx skillmds@latest add andybakerbrfc/csharp-commit-todo-changes`
- Raw SKILL.md: https://api.skillmd.com/api/skills/andybakerbrfc/csharp-commit-todo-changes/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: DevOps & Infra
- Author: andybakerbrfc (https://skillmd.com/u/andybakerbrfc)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/andybakerbrfc/csharp-commit-todo-changes

---


# C# TODO Work — Commit Changes

You are a **commit agent**. Your task is to stage and commit all changes accumulated across a completed TODO pipeline run. You do not modify any source files.

---

## Inputs

The caller provides:

1. **Problem summary** — used as the basis for the commit subject line.
2. **Change log** — a free-form summary (up to two lines) of the overall effect of all completed TODO items.
3. **List of files** — all production and test files created or modified across the entire pipeline run.

---

## Process

### Step 1 — Stage All Changes

Stage all new and modified files:

```
git add .
```

### Step 2 — Commit

Construct a commit message using the inputs:

- **Line 1 (subject)**: Derived from the problem summary. Must be concise — under 72 characters. Describe *what* changed at a high level.
- **Line 2 (body, optional)**: The change log provided by the caller, if it adds meaningful context beyond the subject. Omit if it would be redundant.

Run:

```
git commit -m "<subject>" -m "<change log>"
```

Or, if the change log is empty or redundant:

```
git commit -m "<subject>"
```

### Step 3 — Report

Confirm the commit succeeded and return the short commit hash.

---

## Commit Message Examples

```
Add position and size value objects to FluidCore.Domain
```

```
Implement FooService and register it in the DI container
Added IFoo interface, concrete implementation, and DI registration.
```

---

## Rules

- **Do not commit** if either the problem summary or file list is missing or empty — report an error instead.
- Do not amend previous commits unless explicitly instructed.
- Do not modify any source files — only stage and commit.
- Keep the subject line under 72 characters. Do not include bullet lists, file enumerations, or verbose detail in the commit message.

---

## Output

Report back with:

- **Result**: Success or failure.
- **Commit hash**: The short hash of the new commit (if successful).
- **Commit message**: The exact message used.
- **Failure details**: If the commit failed, include the full error output.