skills.rest
double-coding-lab
double-coding-labOFFICIAL
Explore all skills by this author →
GitHub

repo-dev-check

Audits pending git changes against write-boundary and distribution rules for Flow2Spec repository development.

48|6|Updated Feb 11, 2026
Search Tags:#git#templates#code review#pre-commit#workflow audit#repository governance#flow2spec
One-click install
npx skills add https://github.com/double-coding-lab/Flow2Spec --skill repo-dev-check-double-coding-lab
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: repo-dev-check
Source: https://github.com/double-coding-lab/Flow2Spec/tree/main/.cursor/skills/repo-dev-check
Command: npx skills add https://github.com/double-coding-lab/Flow2Spec --skill repo-dev-check-double-coding-lab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When developing the Flow2Spec repository itself, contributors can accidentally edit files in the wrong place—modifying generated config-root files (.claude/, .cursor/, .codex/) that should instead be changed in templates/, or running distribution commands without explicit user instruction. This Skill catches those mistakes before commit. ## Core Features & Use Cases - Write-Boundary Audit: Classifies every pending git change against a compliance table that distinguishes legitimate edits (templates, package source, repo-exclusive files) from violations (hand-editing init-generated config-root files). - Distribution Discipline Check: Verifies whether the user explicitly requested flow2spec init or npm run sync:agents, and blocks the agent from running distribution commands on its own. - Structured Report: Outputs a summary listing compliant changes, violations with the correct template path to edit instead, and a clear distribution recommendation. - Use Case: Before committing changes in the Flow2Spec repo, run this check to discover that an edit to .claude/skills/f2s-example/SKILL.md should actually have been made in templates/zh-CN/skills/f2s-example/SKILL.md. ## Quick Start Ask the agent to run the dev-workflow self-check on the current pending changes in the Flow2Spec repository.

Frequently Asked Questions about repo-dev-check

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

FAQPage Schema
How do I check if I edited the wrong files in the Flow2Spec repo?▼

Run the repo-dev-check self-check before committing. It lists all pending changes via git status and classifies each file against a compliance table, flagging edits to generated config-root files that should have been made in templates/ instead.

What is the difference between templates and config-root files in Flow2Spec?▼

Files under templates/zh-CN and templates/en-US are the single source of truth distributed to downstream projects. Config-root directories like .claude/, .cursor/, and .codex/ are init-generated products, so hand-editing them is a violation unless the file is repo-exclusive with no template source.

Can this skill run flow2spec init or sync commands automatically?▼

No. The skill only produces judgments and recommendations. It explicitly forbids the agent from running flow2spec init or npm run sync:agents unless the user has explicitly instructed distribution, and it never writes business files itself.

Does repo-dev-check work in downstream projects using Flow2Spec?▼

No. This skill is exclusive to Flow2Spec repository self-development and is never distributed to downstream projects. It only exists in the repo's own .claude/skills/, .cursor/skills/, and .codex/skills/ directories, never in templates/.

Why does the check require reading the constraints rule file first?▼

Step 0 mandates reading the repo-dev-workflow-constraints rule in full because that file is the single source of truth for the boundary rules. Skipping it and judging from memory is treated as a violation of the workflow.

Related Skills

Explore More Software Engineering Skills→
EtanHeyEtanHey

catchup-recent

Review staged and unstaged Git changes with git status --short.

Community
Basic
darrenhindedarrenhinde
4.8k

code-review

Reviews code files for security vulnerabilities, correctness issues, and style violations with severity-ranked findings.

Community
Intermediate
littlebearappslittlebearapps
5

ai-context

Generate and maintain AGENTS.md context files with tool-specific bridges.

Official
Advanced
buchananwillbuchananwill
2

lint-hook-awareness

Summarize UE C++ lint hook rules for auto-caught versus manual review items.

Community
Basic