post-dev-workflow

Orchestrates validation, cross-layer synchronization, testing, and commit preparation after code changes.

1.6k|221|Updated Oct 28, 2025
One-click install
npx skills add https://github.com/ZeroDeng01/sublinkPro --skill post-dev-workflow-zerodeng01
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: post-dev-workflow
Source: https://github.com/ZeroDeng01/sublinkPro/tree/main/.agents/skills/post-dev-workflow
Command: npx skills add https://github.com/ZeroDeng01/sublinkPro --skill post-dev-workflow-zerodeng01

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve? After finishing code changes, developers often skip linting, forget to update bilingual documentation, miss cross-layer impacts between backend and frontend, or commit without proper test coverage and commit messages. This Skill enforces a mandatory, phased post-development workflow so no validation step is skipped before work is declared complete. ## Core Features & Use Cases - Phased Validation Pipeline: Runs code validation (gofmt, golangci-lint, yarn lint/build), cross-layer synchronization checks, documentation sync (English and Chinese), and test execution in a defined sequence with explicit exit criteria per phase. - Commit Message Standardization: Generates conventional commit messages (type, scope, subject, body, footer) using a detailed guide and a reusable git commit template. - Mandatory Pre-Commit Gate: Requires a final pre-commit-check phase before staging, verifying no sensitive files or runtime data are committed, and stages changes for user review without auto-committing. - Use Case: After modifying a Go API endpoint and its React frontend consumer, the workflow verifies lint and tests pass, confirms the API reference documentation is updated in both languages, adds regression tests, and prepares a formatted commit message for user approval. ## Quick Start Run the post-development workflow to validate, synchronize, and prepare my just-completed code changes for commit.

Frequently Asked Questions about post-dev-workflow

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

FAQPage Schema
How do I validate Go and React code changes before committing?

Run gofmt and golangci-lint for Go files, plus yarn lint and yarn build for the React frontend. The workflow defines these as Phase 1 with explicit exit criteria requiring zero lint errors and passing tests before proceeding.

What is a conventional commit message format?

Conventional commits use the format type(scope): subject, such as feat(airports): add batch update. Types include feat, fix, docs, refactor, test, chore, style, and perf, with an optional body and footer referencing issues.

How do I keep backend API and frontend code synchronized?

When a backend endpoint changes, update the frontend API client functions, affected components, and the API reference documentation. The cross-layer sync rules map each backend change type to its required frontend and documentation updates.

When can documentation synchronization be skipped?

Documentation sync can be skipped only for pure internal refactoring with no user-visible changes, bug fixes that restore documented behavior, or test-only changes. The skip reason must be documented in the change summary.

Why does the workflow require a separate pre-commit check after validation?

Files may change during documentation or test updates after initial validation. The pre-commit phase re-runs format, lint, and test commands, verifies git staging contains no sensitive files or runtime data, and confirms the commit message format.

Does this workflow commit changes automatically?

No, the workflow stages changes with git add and presents a summary with a prepared commit message, but never auto-commits. Users review staged changes with git diff --cached, perform manual testing, and commit when satisfied.