I have processed your idea for the Git Commit Architect skill. I've defined a deterministic workflow that analyzes diffs, applies conventional commit standards, and generates a structured marketplace package.

Preflight & Listing Pack: git-commit-architect

1. Completed SKILL.md

name: git-commit-architect
description: Generates conventional commit messages by analyzing staged git diffs.
version: 1.0.0
license: MIT

Git Commit Architect

Purpose

Turn messy code changes into structured, meaningful commit messages following the Conventional Commits specification.

Workflow

1. Diff Analysis: Read the provided git diff to identify affected files and change types.
2. Impact Assessment: Determine if the change is a feature, fix, refactor, or chore.
3. Drafting: Generate a summary line (< 50 chars) and a body explaining the 'why'.
4. Validation: Check against length constraints and breaking change flags.

2. Marketplace Listing Metadata

• Title: Git Commit Architect
• Summary: Automate conventional commit message generation from staged git diffs.
• Use Cases:
  • Standardize commit history across distributed engineering teams.
  • Generate body descriptions that explain the intent behind complex diffs.
  • Flag breaking changes automatically based on signature modifications.

3. Preflight Report

• Quality Score: 42/45 (Strong)
• Strengths: High utility, narrow scope, clear output format.
• Risks: Large diffs may exceed context windows; recommended a 200-line limit.
• Security: No dangerous shell execution detected in instructions.

Next steps

1. Review the generated SKILL.md for any specific project naming conventions.
2. Test the "messy input" example with a large refactor diff.
3. Upload the listing metadata to your Agensi draft.