qb

Audit backend codebases against styleguide and security policies.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/madebymlai/feldspar --skill qb-madebymlai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qb
Source: https://github.com/madebymlai/feldspar/tree/main/.claude/skills/qb
Command: npx skills add https://github.com/madebymlai/feldspar --skill qb-madebymlai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured process for auditing backend code against styleguide, security, and testing standards, eliminating manual, inconsistent reviews.

Core Features & Use Cases

  • Scope Evaluation: Analyzes a given directory or file to identify audit targets, filtering out irrelevant test and mock files.
  • Team Orchestration: Automatically creates a QA team, assigns grouped files to auditors, and coordinates their work.
  • Cleanup Automation: Sends shutdown requests and removes the team once all audits finish.
  • Use Case: Run the skill on a microservice's source folder to ensure API routes follow best practices, data access is secure, and legacy __tests__ are migrated to the new naming convention.

Quick Start

Run the qb skill on the target directory to audit backend files and receive a comprehensive QA report.

Frequently Asked Questions about qb

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

FAQPage Schema
How do I automate backend code audits against security and styleguide standards?

Automate backend code audits by applying the skill to a target directory to evaluate API routes, data access patterns, and test organization against your styleguide and security policies.

What is the best way to migrate legacy test file naming conventions in a backend project?

Migrating legacy test naming conventions is handled during the backend audit process, which identifies outdated `__tests__` structures and evaluates test organization against new standards.

How does automated QA code analysis evaluate a microservice source folder?

Automated QA analysis evaluates a microservice source folder by filtering out irrelevant mock files, identifying audit targets, and coordinating a team of auditors to review grouped files.

Can I run an automated backend QA audit on individual files instead of an entire directory?

Yes, you can run the automated backend QA audit on individual files by providing the specific file path as an argument instead of a directory.

Do I need to manually configure QA team orchestration for a backend security audit?

No, manual QA team orchestration is not required; the skill automatically creates a QA team, assigns grouped files to auditors, and sends shutdown requests once all audits finish.

What are the limitations of automated styleguide and security audits for backend codebases?

Automated backend audits require a valid path argument to function and focus solely on styleguide, security, and testing standards, filtering out test and mock files from the audit scope.