q-kdb-code-review

What This Skill Does

q-kdb-code-review is an specialized AI-powered analysis tool designed specifically for the Q/kdb+ programming language. Because Q is exceptionally terse and relies heavily on implicit typing and vector operations, standard linting tools often miss domain-specific performance bottlenecks and logical pitfalls. This skill acts as a expert-level pair programmer, scanning your codebase for common quantitative finance anti-patterns. It evaluates code against three distinct profiles: standard correctness, performance-oriented strict mode, and a security-focused audit. It identifies issues ranging from rank errors and type mismatches to complex performance killers like N-squared join operations and missing sorted attributes. By utilizing intelligent routing, it ensures that simple queries are handled rapidly while complex algorithmic signals are processed by high-reasoning models.

Installation

1. Ensure you have the OpenClaw agent installed and configured.
2. Obtain a free API key from as-trai.com.
3. Set your environment variables:
   • export ASTRAI_API_KEY="your_key_here"
   • Optionally configure ANTHROPIC_API_KEY or OPENAI_API_KEY for BYOK (Bring Your Own Keys) capabilities.
4. Run the install command in your terminal: clawhub install openclaw/skills/skills/beee003/q-kdb-code-review.

Use Cases

• Production Readiness: Use the strict mode before merging pull requests to ensure your high-frequency trading ticker plant is optimized for low latency.
• Security Auditing: Run the security mode on any gateway or tick-handler that accepts external IPC connections to prevent code injection attacks or unauthorized system access.
• Refactoring: Use the basic review mode to identify legacy code that uses inefficient loops or outdated syntax that can be vectorized for better performance.

Example Prompts

1. "/review-q --file historical_data_processor.q"
2. "/review-q --strict, please check for any missing g# or s# attributes in my table schema definitions."
3. "/review-q --focus security, scan my .z.pg and .z.ps handlers for potential vulnerabilities."

Tips & Limitations

• Tip: Always run in strict mode if you are preparing code for a production environment to ensure that peach parallelism is utilized where appropriate.
• Limitation: The skill provides recommendations based on best practices; always benchmark your code with (time) in the kdb+ console before deploying major refactors to production.
• Tip: When using the security mode, ensure you review any flagged IPC handlers manually to confirm if the access patterns align with your network security policy.