repo-dev-check

Verify file placement and repository consistency in Flow2Spec using git operations.

40|4|Updated Feb 11, 2026
One-click install
npx skills add https://github.com/Lands-1203/Flow2Spec --skill repo-dev-check
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: repo-dev-check
Source: https://github.com/Lands-1203/Flow2Spec/tree/main/.cursor/skills/repo-dev-check
Command: npx skills add https://github.com/Lands-1203/Flow2Spec --skill repo-dev-check

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps developers in Flow2Spec ensure that their code modifications adhere to the correct file locations and maintain consistency between the two repositories, preventing common errors and ensuring smooth development workflows.

Core Features & Use Cases

  • File Location Verification: Checks if pending code changes are made in the correct file locations, such as templates, source code, or specific knowledge bases.
  • Repository Consistency: Ensures that changes in one repository are consistent with the other, preventing "double-writes" and other synchronization issues.
  • Automated Checks: Automatically runs checks before code commits or on demand, providing immediate feedback on potential issues.

Quick Start

Run the repo-dev-check skill to verify the correctness of your code modifications in the Flow2Spec development workflow.

Frequently Asked Questions about repo-dev-check

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

FAQPage Schema
How do I verify file placement and repository consistency before a code commit?

To verify repository consistency before a commit, run automated checks that validate file placement against predefined constraints and prevent synchronization issues like double-writes across repositories.

What is repository consistency checking in a development workflow?

Repository consistency checking ensures that code modifications adhere to correct file locations and maintain synchronization between multiple repositories, preventing common errors during development.

Do I need git operations to check code modifications in my repository?

Yes, git operations are required to perform these repository consistency checks, as the verification process evaluates pending code changes and file modifications against predefined development rules.

How do I prevent double-writes when working with multiple repositories?

To prevent double-writes across multiple repositories, use consistency checks that automatically verify changes in one repository align with the other, providing immediate feedback before code commits.

Can I run consistency checks on demand during version control workflows?

Yes, you can run consistency checks on demand or automatically before code commits, verifying that pending changes in templates, source code, or knowledge bases adhere to development rules.