skills.rest
mcsdodo
mcsdodoCOMMUNITY
Explore all skills by this author →
GitHub

verify

Run tests, check git status, and confirm changelog updates for completion readiness.

Updated Dec 28, 2025
Search Tags:#changelog#verify#code-review#tests#git-status#release-readiness
One-click install
npx skills add https://github.com/mcsdodo/kniha-jazd --skill verify-mcsdodo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verify
Source: https://github.com/mcsdodo/kniha-jazd/tree/main/.claude/skills/verify-skill
Command: npx skills add https://github.com/mcsdodo/kniha-jazd --skill verify-mcsdodo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams often mark work as complete without a formal verification. This skill enforces a rigorous pre-closure check by running the project's test suite, inspecting the git working tree, and validating that changelog entries exist for user-visible updates.

Core Features & Use Cases

  • Run tests to ensure code integrity across the project.
  • Inspect git status to confirm no unstaged changes.
  • Verify that a new changelog entry exists for the user-visible release.
  • Use Case: PR closure, sprint completion, and release readiness require this verification before marking work as done.

Quick Start

Run the verify workflow before marking a task complete to ensure tests pass, the repo is clean, and the changelog is updated.

Frequently Asked Questions about verify

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

FAQPage Schema
How do I verify release readiness before marking a task complete?▼

Release readiness verification requires running the local test suite, checking git status for unstaged changes, and confirming a changelog entry exists for user-visible updates before marking work done.

What is the best way to automate pre-closure checks for a pull request?▼

Pre-closure checks for a pull request enforce a rigorous verification workflow by validating code integrity through tests, inspecting the git working tree, and ensuring documentation updates match the code changes.

How does checking git status prevent incomplete work from being merged?▼

Checking git status prevents incomplete work from merging by inspecting the working tree to confirm no unstaged or pending changes remain, ensuring the repository is clean before closure.

Do I need a changelog entry for every code review and sprint completion?▼

A changelog entry is required for user-visible updates during sprint completion and code reviews, enforcing the documentation of release changes alongside passing tests and a clean git status.

Can I use this verification workflow for general software development or only releases?▼

This verification workflow applies to general software development workflows, code reviews, and release preparations, ensuring tests pass and changes are committed before any task closure.

Related Skills

Explore More Software Engineering Skills→
LuizfbmLuizfbm
1

finishing-a-development-branch

Verify tests and merge feature branches with git worktree cleanup.

Community
Advanced
monomono
5.5k

release-publish

Publish SkiaSharp packages to NuGet.org and finalize releases.

Official
Advanced
lehuuhau1231lehuuhau1231

lint-and-validate

Run linting and type checking across multiple programming ecosystems.

Community
Intermediate
Magnatrix-LabMagnatrix-Lab
1

repo-health

Monitor CI pipeline status, dependency vulnerabilities, disk space, and backup integrity.

Community
Intermediate