Implement and review Python code against BORO Quick Style Guide rules.
npx skills add https://github.com/OntoLedgy/ol_ai_context_library --skill ob-engineer
Please help me install this Agent Skill. Skill: ob-engineer Source: https://github.com/OntoLedgy/ol_ai_context_library/tree/main/skills/ob-engineer Command: npx skills add https://github.com/OntoLedgy/ol_ai_context_library --skill ob-engineer
This Skill eliminates ambiguity and inconsistency when implementing or reviewing Python code for OB (Ontoledgy/BORO) ontological engineering workflows, where standard PEP 8 conventions conflict with the strict BORO Quick Style Guide requirements for platform-specific codebases. It ensures all code adheres to the correct coding standards, platform library usage, and quality validation rules for OL platform projects.
python-data-engineer skill with BORO-specific overrides, including 20-character line lengths, plural CamelCase class names, one public function per file, mandatory type annotations, no hardcoded strings, and double-underscore private methods.Use the ob-engineer skill to implement a BORO-compliant Python data export module for your Ontoledgy codebase, then run the full BORO quality gate suite to verify all style, type, and test checks pass.
High-intent search queries and answers about installing and using this skill.
To enforce BORO style compliance in Python code, apply the BORO Quick Style Guide which overrides PEP 8 with strict rules. These include 20-character line lengths, plural CamelCase class names, one public function per file, and explicit type annotations for Ontoledgy/BORO platform projects.
You cannot use standard Python utilities for Ontoledgy and BORO codebases without checking imports. The platform requires specific libraries for file, folder, and utility operations, automatically detecting whether the target is an Ontoledgy or BORO project variant to enforce correct platform usage.
Quality gates for BORO-compliant Python code validation require running strict mypy, ruff, and pytest checks. These tools enforce mandatory type annotations, structural rules like one public function per file, and comprehensive testing to satisfy the ontological engineering standards.
To implement Python code for ontological engineering workflows that passes BORO review, follow the BORO Quick Style Guide overrides. Ensure your code uses plural CamelCase class names, double-underscore private methods, no hardcoded strings, and explicit type annotations before running automated compliance checks.
Ontoledgy Python code fails style checks despite passing standard PEP 8 linters because BORO projects use a stricter Quick Style Guide. PEP 8 conventions are overridden by requirements for 20-character line lengths, plural CamelCase class names, and double-underscore private methods.
You need explicit type annotations for every function in a BORO Python codebase to pass strict mypy validation. The BORO Quick Style Guide mandates type annotations alongside structural rules like one public function per file to ensure ontological engineering quality.
kobogithubGuide modern Python development with uv, ruff, mypy, and pytest.
EstomGenerate type-safe async Python 3.11+ code with pytest suites and mypy --strict compliance.
CallMeLuigiv2Enforce Rust naming, formatting, and lint conventions during code reviews.
PriyanshKuniyalEnforce PEP 8 formatting, naming, and documentation standards in Python code.