verify-functionality

Generate a step-by-step manual verification guide from git diff and log outputs.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/meganide/claude --skill verify-functionality
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verify-functionality
Source: https://github.com/meganide/claude/tree/main/skills/verify-functionality
Command: npx skills add https://github.com/meganide/claude --skill verify-functionality

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill analyzes the current branch against the main reference and generates a clear, step-by-step manual verification guide for changes.

Core Features & Use Cases

  • Automated Verification Guide: Creates a human-friendly checklist that can be saved as verification.md in the appropriate specs folder.
  • Branch-diff Based: Compares current branch to main to determine changed files and commit summaries.
  • Spec-folder Targeting: Determines the target spec folder based on branch context or changed files, or asks the user when unclear.

Quick Start

Use the verify-functionality skill to generate a verification guide for the current repository changes.

Frequently Asked Questions about verify-functionality

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

FAQPage Schema
How do I generate a manual verification checklist from a git diff?

To generate a manual verification checklist, you need a Git repository with a main or origin/main baseline. The tool reads git diff and git log outputs to create a step-by-step guide saved as a Markdown file.

How do I create a verification guide for code changes across branches?

Creating a verification guide for code changes involves comparing your current branch to main. The tool analyzes changed files and commit summaries to output a human-friendly checklist in your specs folder.

Where does the generated verification guide get saved in the repository?

The generated verification guide is saved as a Markdown file named verification.md. It is placed inside the appropriate specs folder, typically structured as specs/<feature>/verification.md.

Can I use this to generate a quality assurance guide without a main branch?

No, you cannot generate a quality assurance guide without a baseline. The process requires a Git repository with either a local main or remote origin/main branch to compare current changes against.

What happens if the target specs folder for the verification guide is unclear?

If the target specs folder is unclear, the tool attempts to determine the destination based on branch context or changed files. If ambiguity remains, it will ask the user to specify the correct feature folder.