skills.rest
HiveSpaceTeam
HiveSpaceTeamOFFICIAL
Explore all skills by this author →
GitHub

verify-story

Audit backend code changes against planned HiveSpace feature tasks.

Updated Jul 3, 2025
Search Tags:#backend#verification#code audit#task coverage#HiveSpace
One-click install
npx skills add https://github.com/HiveSpaceTeam/hivespace.microservice --skill verify-story
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verify-story
Source: https://github.com/HiveSpaceTeam/hivespace.microservice/tree/main/.agent-source/skills/verify-story
Command: npx skills add https://github.com/HiveSpaceTeam/hivespace.microservice --skill verify-story

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill audits current backend changes against planned HiveSpace feature tasks, ensuring that the implementation aligns with the defined requirements without editing files.

Core Features & Use Cases

  • Audit Backend Changes: Compare current backend changes against planned tasks.
  • Verification-Only: Prevents edits, staging, committing, or other file modifications.
  • Use Case: Verify that all necessary backend changes have been implemented for a new HiveSpace feature before deployment.

Quick Start

Run the verify-story skill to audit changes for the "new-feature" HiveSpace feature.

Frequently Asked Questions about verify-story

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

FAQPage Schema
How do I audit backend code changes against planned feature tasks?▼

Auditing backend changes involves comparing current code modifications against planned feature task definitions to verify alignment and coverage. This process requires Git and access to spec files.

Does the verification process modify or stage my backend files?▼

No, the verification process is strictly read-only. It prevents any edits, staging, committing, or other file modifications while auditing backend changes against planned tasks.

What do I need to check backend task coverage for HiveSpace features?▼

To verify backend task coverage for HiveSpace features, you need Git and access to HiveSpace spec files. These provide the baseline definitions for comparing current code changes during the audit.

When should I verify that backend changes align with feature requirements?▼

You should verify backend changes align with feature requirements before deployment. This ensures all necessary backend modifications have been implemented according to the planned HiveSpace feature task definitions.

Can I verify task coverage for backend changes without committing to Git?▼

Yes, you can verify task coverage without committing because the process is verification-only. It audits current backend changes against planned tasks without editing, staging, or committing files.

Related Skills

Explore More Software Engineering Skills→
WindXRanWindXRan

scope-check

Compare planned baselines against current codebase state to detect scope creep.

Community
Intermediate
KrismithReddy12KrismithReddy12

land-and-deploy

Merge pull requests, trigger CI/CD pipelines, and validate production health.

Community
Advanced
alvarovillalbaaalvarovillalbaa

frontend

Implement React and Next.js frontend UI with accessibility and performance checks.

Community
Advanced
aaddrickaaddrick
5.3k

lint

Lint shell scripts with shellcheck and GitHub Actions workflows with actionlint.

Community
Basic