development-workflow

Name: development-workflow
Availability: InStock
Author: massCodeIO

Run scoped lint and tests on touched files with mandatory follow-ups.

6.9k|262|Updated Mar 29, 2022

Search Tags:#workflow #pnpm #test #lint #scoped #locale-sync

Ready to run

npx skills add https://github.com/massCodeIO/massCode --skill development-workflow-masscodeio

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: development-workflow
Source: https://github.com/massCodeIO/massCode/tree/main/.agents/skills/development-workflow
Command: npx skills add https://github.com/massCodeIO/massCode --skill development-workflow-masscodeio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enforces scoped lint and tests to ensure changes stay localized and safe.

Core Features & Use Cases

Lint and test only on touched files or directories.
Enforce scoped commands like pnpm lint <path> and pnpm test <path>.
Apply mandatory follow-up steps after API or locale changes, such as code generation or locale synchronization.

Quick Start

Follow linting and testing only on affected files and apply the required follow-up steps after making API or locale changes.

Frequently Asked Questions about development-workflow

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

FAQPage Schema

How do I run lint and tests only on touched files in a pull request?▼

To run scoped lint and tests on touched files, execute commands like pnpm lint <path> and pnpm test <path>. This ensures changes stay localized and safe by validating only the affected directories.

How do I enforce mandatory follow-up steps after API or locale changes?▼

You can enforce mandatory follow-up steps like code generation or locale synchronization after API or locale changes. This workflow guardrail ensures dependent updates are never skipped during development.

What is scoped workflow enforcement for localized code changes?▼

Scoped workflow enforcement restricts lint and test execution to touched files or directories. It prevents unrelated failures and ensures localized changes remain safe across pull requests and local development tasks.

Can I use pnpm for selective test execution across specific directories?▼

Yes, you can use pnpm for selective test execution by targeting specific paths. Running pnpm test <path> validates only the affected directories, satisfying requirements for localized and safe selective execution.

What is the best way to automate locale sync as a required pull request follow-up?▼

The best way to automate locale sync is by enforcing it as a mandatory follow-up step within your scoped workflow. This guardrail ensures locale synchronization automatically runs after relevant code changes.

Does scoped linting work with local tasks or only pull requests?▼

Scoped linting works with both pull requests and local tasks. It enforces localized checks using pnpm lint <path> across your entire development workflow to keep changes safe regardless of environment.