ai-settings

Analyze git diffs to generate mode-specific delivery-quality artifacts.

Updated Mar 24, 2026
One-click install
npx skills add https://github.com/tombelial666/test --skill ai-settings
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ai-settings
Source: https://github.com/tombelial666/test/tree/main/.cursor/skills/ai-settings
Command: npx skills add https://github.com/tombelial666/test --skill ai-settings

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

AI Settings provides structured, mode-driven output to support ETNA_TRADER delivery quality by analyzing the current git diff and changed files to produce standardized artifacts.

Core Features & Use Cases

  • Mode-driven outputs: supports RELEASE_NOTES, ACCEPTANCE_CRITERIA, REPO_STYLE_ALIGNMENT, UNIT_TEST_OPPORTUNITIES, and PRE_COMMIT_CHECK to cover multiple delivery stages.
  • Diff context consumption: gathers diff data and reads changed files to generate targeted reports.
  • Operational workflow: loads the appropriate mode from arguments and returns a deterministic artifact for downstream tasks (e.g., Jira, CI checks).

Quick Start

Use the AI Settings workflow to analyze the current git diff and generate a mode-specific delivery-quality report.

Frequently Asked Questions about ai-settings

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate release notes from a git diff?

Generating release notes from a git diff involves parsing the current diff and changed files to produce structured, deterministic artifacts. A mode-driven analysis tool reads this diff context to output standardized reports suitable for downstream delivery workflows.

What is mode-driven git diff analysis for code quality?

Mode-driven git diff analysis is the process of parsing diff context and changed files to produce deterministic outputs for specific delivery stages. It supports multiple modes including release notes, acceptance criteria, repo style alignment, unit-test opportunities, and pre-commit checks.

How do I extract acceptance criteria from a git diff?

Extracting acceptance criteria from a git diff requires loading the appropriate mode and gathering pre-work diff context. The process reads changed files to generate a targeted, deterministic artifact that satisfies specific delivery quality requirements.

Can I automate pre-commit checks using git diff context?

Yes, you can automate pre-commit checks by parsing arguments for the pre-commit mode and analyzing the current git diff. This generates deterministic outputs that function as CI checks to enforce delivery quality standards before changes are committed.

Does this approach work for ETNA_TRADER delivery quality workflows?

Yes, this mode-driven git diff analysis specifically solves the problem of producing structured output for ETNA_TRADER delivery quality. It analyzes current diffs and changed files to generate standardized artifacts tailored to the ETNA_TRADER platform's downstream tasks.

How do I identify unit test opportunities from changed files?

Identifying unit test opportunities from changed files involves selecting the unit-test mode and reading the current git diff. The analysis generates deterministic artifacts that highlight specific areas within the changed code that require test coverage.