generate

Generate atomic commits with npm run verify for each feature or fix.

9|3|Updated Jan 29, 2022

Search Tags:#automation #verification #code-quality #generator #atomic-commits #git-workflow

Ready to run

npx skills add https://github.com/I194/PMTools_2.0 --skill generate-i194

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: generate
Source: https://github.com/I194/PMTools_2.0/tree/main/.claude/skills/generate
Command: npx skills add https://github.com/I194/PMTools_2.0 --skill generate-i194

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generator agent helps teams implement features and fixes one at a time with atomic commits and built-in verification to maintain code quality.

Core Features & Use Cases

Atomic, single-feature commits with clear messages
Run verification after every change (typecheck, lint, format)
Maintain a merge-ready state
Provide a final verification prompt for the Evaluator agent after all work is done

Quick Start

Begin by selecting a feature or fix, implement it, run npm run verify, and commit atomically with a descriptive message.

Frequently Asked Questions about generate

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

FAQPage Schema

How do I automate atomic commits for single feature delivery?▼

To automate atomic commits, implement a single feature or fix, run npm run verify to validate code quality through typecheck, lint, and format checks, and commit the isolated change with a descriptive message to maintain a merge-ready state.

What is an atomic commit in a git workflow?▼

An atomic commit isolates a single feature or fix into one self-contained change. This ensures each commit remains verifiable with npm run verify, maintains code quality, and keeps the repository in a merge-ready state throughout development.

Does the generator workflow require npm run verify for code quality?▼

Yes, running npm run verify is required after every feature implementation to enforce automated code quality. It validates typecheck, lint, and format checks before any atomic commit is finalized, ensuring the codebase remains stable and merge-ready.

Can I use this automated commit workflow for PMTools 2.0 development?▼

Yes, this automated workflow is specifically designed for software teams working on PMTools 2.0. It ensures disciplined feature delivery by generating verifiable atomic commits and providing a final verification prompt for the Evaluator agent after work is done.

How do I maintain a merge-ready state when implementing features?▼

To maintain a merge-ready state, implement features one at a time, run npm run verify for validation, and commit atomically with descriptive messages. This ensures each isolated change passes typecheck, lint, and format checks before integration.

What is the best way to verify code quality before a git commit?▼

The best way to verify code quality before a git commit is running npm run verify. This automated validation step executes typecheck, lint, and format checks, ensuring the atomic commit meets the required code quality standards before integration.