skills.rest
ormastes
ormastesCOMMUNITY
Explore all skills by this author →
GitHub

Coding Skill - Workflow & Standards

Compile, lint, and auto-fix Simple (.spl) source code with enforced standards.

Updated May 27, 2026
Search Tags:#linting#coding standards#auto-fix#test documentation#simple language#build workflow
One-click install
npx skills add https://github.com/ormastes/Spipe --skill coding-skill-workflow-standards
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Coding Skill - Workflow & Standards
Source: https://github.com/ormastes/Spipe/tree/main/doc/00_llm_process/skill_command/skills/claude/lib/coding
Command: npx skills add https://github.com/ormastes/Spipe --skill coding-skill-workflow-standards

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures Simple code changes follow a predictable workflow for building, linting, auto-fixing, and documenting tests, reducing broken builds and inconsistent standards.

Core Features & Use Cases

  • Compile and fix loop: Provides a reliable sequence for debugging builds, running lint checks, and applying deterministic auto-fixes.
  • Strict coding standards: Enforces minimal, requested changes and bans unnecessary refactors or leftover removed code.
  • Test documentation rules: Requires documentation-first test docstrings (no documentation-breaking println usage) for clearer, reviewable behavior.
  • Scripting policy: Limits scripts to Simple (.spl) and specifies how to run them using the Simple command runner.

Quick Start

Run the build and lint, then apply fixes to a specific .spl file while ensuring tests use docstring markdown for documentation.

Frequently Asked Questions about Coding Skill - Workflow & Standards

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

FAQPage Schema
How do I run lint and auto-fix on Simple (.spl) source code?▼

To run lint and auto-fix on Simple (.spl) source code, execute the build and lint commands in sequence, then apply deterministic auto-fixes to correct errors. This workflow ensures your Simple scripts compile correctly and adhere to coding standards.

What is the best way to document tests in Simple (.spl) scripts?▼

The best way to document tests in Simple (.spl) scripts is by using documentation-first test docstrings. You must avoid using println for documentation, ensuring clearer, reviewable test behavior that meets the required coding standards.

Can I execute non-Simple scripts using the Simple command runner?▼

No, you cannot execute non-Simple scripts using the Simple command runner. The scripting policy strictly limits execution to Simple (.spl) source code files only, preventing the use of other script formats within the build workflow.

Why should coding changes follow minimal-diff rules when applying lint fixes?▼

Coding changes should follow minimal-diff rules to enforce strict coding standards and prevent unnecessary refactoring. Banning leftover removed code keeps the source clean, ensuring predictable builds and consistent, requested modifications.

What is the correct command sequence for debugging Simple code builds?▼

The correct command sequence for debugging Simple code builds involves running the build process, executing lint checks, and then applying deterministic auto-fixes. This predictable workflow loop reduces broken builds and maintains consistent standards.

Related Skills

Explore More Software Engineering Skills→
danghungtb26danghungtb26
3

project-conventions

Enforce naming and folder structure conventions for React TypeScript admin templates.

Community
Basic
curtislmartincurtislmartin

swift-testing-pro

Analyze Swift Testing suites and provide before/after code fixes.

Community
Advanced
lucasolslucasols

fix-lint

Detect and correct ESLint violations and type errors in TypeScript projects.

Community
Intermediate
D0NMEGAD0NMEGA
8

plankton-code-quality

Automate formatting and linting on file edits via PostToolUse hooks.

Community
Advanced