coding-standards

Enforce PHP and JavaScript coding standards with docstrings and DB-change tracking.

Updated Jun 1, 2026
One-click install
npx skills add https://github.com/weerachai8266/CWT-maintenance_V2 --skill coding-standards-weerachai8266
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: coding-standards
Source: https://github.com/weerachai8266/CWT-maintenance_V2/tree/main
Command: npx skills add https://github.com/weerachai8266/CWT-maintenance_V2 --skill coding-standards-weerachai8266

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This policy ensures all PHP and JavaScript code follows a consistent standard by requiring full docstrings, banning inline scripts, and enforcing DB-change tracking.

Core Features & Use Cases

  • Docstring enforcement: every function must include a Description, Args, and Returns.
  • No inline scripts: all JavaScript must reside in external files loaded via script tags.
  • DB-change awareness: any database schema changes must be documented in sql/update.sql for traceability.

Quick Start

Provide a compliant PHP/JS function that adheres to the project’s coding standards.

Frequently Asked Questions about coding-standards

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

FAQPage Schema
How do I enforce PHP and JavaScript coding standards across a web project?

To enforce PHP and JavaScript coding standards, require full docstrings for every function, ban inline scripts by moving JavaScript to external files, and track database schema changes in sql/update.sql.

What should PHP function docstrings include to pass code review?

PHP function docstrings must include a Description, Args, and Returns to pass code review and ensure all functions and modules maintain consistent documentation standards across the codebase.

How do I track database schema changes for PHP web projects?

Track database schema changes by documenting any modifications in sql/update.sql, which ensures traceability and maintains a historical record of all database updates across the project.

Why should I move inline JavaScript to external files?

You should move inline JavaScript to external files because coding standards ban inline scripts, requiring all JavaScript to reside in external files loaded via script tags to improve code quality and maintainability.

Can I apply these coding standards to functions across all modules?

Yes, you can apply these coding standards to all functions and modules across the entire codebase, ensuring every PHP and JavaScript component complies with docstring, inline script, and database change tracking requirements.

What's the best way to document database changes during code review?

The best way to document database changes during code review is to record all schema modifications in sql/update.sql, providing full traceability and ensuring all database updates are tracked alongside PHP and JavaScript code changes.