Enforce CAPRI GAMS coding conventions for writing, reviewing, and refactoring GAMS code.
npx skills add https://github.com/chrispahm/gams-ide --skill capri-gams-style
Please help me install this Agent Skill. Skill: capri-gams-style Source: https://github.com/chrispahm/gams-ide/tree/main/skills/capri-gams-style Command: npx skills add https://github.com/chrispahm/gams-ide --skill capri-gams-style
This skill ensures GAMS code adheres to the strict CAPRI coding conventions, promoting consistency, maintainability, and readability across the project.
Review the provided GAMS code snippet for adherence to CAPRI coding conventions.
High-intent search queries and answers about installing and using this skill.
You can review GAMS code against the official CAPRI "Red Book" conventions, which cover naming, set usage, code structure, indentation, flow control, and error trapping to ensure consistency and maintainability.
The CAPRI GAMS style guide rules enforce specific conventions for naming, set usage, indentation, compile-time directives, and comments. Adhering to these rules promotes readability and maintainability across the CAPRI modeling project.
Yes, you can refactor GAMS code by analyzing it against the "Red Book" rules for naming, structure, indentation, comments, and error trapping, correcting deviations to align with CAPRI conventions.
To generate new GAMS modules for the CAPRI model that pass code review, produce code that strictly follows CAPRI conventions for flow control, metadata, and version control practices outlined in the style guide.
Yes, the CAPRI GAMS style guide covers error trapping and compile-time directives. It enforces specific conventions for these elements to ensure robust code structure and execution within the CAPRI model.
chrispahmCreate and extend CAPRI model modules using GAMS conventions.
chrispahmDocument agricultural policy instruments and their GAMS implementation in CAPRI.
R2W1csLint and validate JavaScript and Python code for syntax and style issues.
AbeJitsuApply user-defined formatting standards across code, documentation, and content outputs using ESLint and Prettier.
