skills.rest
I194
I194COMMUNITY
Explore all skills by this author →
GitHub

write-verify

Generate a verify-fixes.md prompt from git history and diffs.

9|3|Updated Jan 29, 2022
Search Tags:#automation#git#versioning#prompts#verify#evaluator
One-click install
npx skills add https://github.com/I194/PMTools_2.0 --skill write-verify
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: write-verify
Source: https://github.com/I194/PMTools_2.0/tree/main/.claude/skills/write-verify
Command: npx skills add https://github.com/I194/PMTools_2.0 --skill write-verify

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the creation of a verify-fixes.md prompt for the Evaluator from the most recent repository changes, reducing manual prompt crafting.

Core Features & Use Cases

  • Generates a ready-to-paste /evaluate prompt from git history and diffs.
  • Reads package.json to determine the current version.
  • Saves the resulting prompt to test-data/v{version}/verify-fixes.md for traceability.

Quick Start

Run the analysis workflow to generate a verifier prompt from the latest commits and diffs.

Frequently Asked Questions about write-verify

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

FAQPage Schema
How do I generate verification prompts from git history automatically?▼

To generate verification prompts automatically, this Skill reads recent commit history and diffs using git log and git diff commands. It extracts the changes and formats them into a ready-to-paste verifier prompt for the Evaluator.

How do I create an evaluate prompt from recent commit diffs?▼

Creating an evaluate prompt from recent commit diffs is done by executing git log --oneline -20 and git diff main...HEAD --stat. The Skill processes these diff outputs to build the verification prompt automatically without manual formatting.

Does this verifier prompt generator work with Git repositories?▼

Yes, this verifier prompt generator works specifically with Git repositories. It requires Git to execute log and diff commands for analyzing recent repository changes before creating the verification file.

Where does the generated verify-fixes prompt file get saved?▼

The generated verify-fixes prompt file gets saved to test-data/v{version}/verify-fixes.md. The version number is determined by reading the package.json file located in the repository root.

Why do I need to read package.json for versioning test data?▼

Reading package.json for versioning test data ensures the generated verify-fixes.md prompt is saved to a versioned directory like test-data/v{version}. This provides traceability for fixes across different software releases.

Related Skills

Explore More Software Engineering Skills→
hiddink-aihiddink-ai
1

hiddink-harness:npm-version

Automate npm package version bumps, changelogs, and git tags.

Official
Intermediate
DisposableByDefaultDisposableByDefault
1

Test and Fix

Run pytest unit tests, diagnose failures, and iterate fixes until stable.

Official
Advanced
benmaierbenmaier

Create data science agents

Design and validate data-science agent prompts and parallel-agent configurations.

Community
Advanced
viktorbezdekviktorbezdek
10

git-workflow

Automate Git commit formatting, branch organization, and release note generation.

Community
Advanced