daily-dig

Find defects in the Breadboard codebase and produce tests, lint rules, or codemods.

409|75|Updated Dec 12, 2023
One-click install
npx skills add https://github.com/breadboard-ai/breadboard --skill daily-dig
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: daily-dig
Source: https://github.com/breadboard-ai/breadboard/tree/main/.agent/skills/daily-dig
Command: npx skills add https://github.com/breadboard-ai/breadboard --skill daily-dig

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

A proactive bug hunt across the Breadboard codebase. Pick an area, go looking, and produce a concrete artifact (test, lint rule, or codemod) for anything you find.

Core Features & Use Cases

  • Provides a structured approach to locating defects across recently changed files, complex modules, and flagged code areas.
  • Encourages producing tangible outputs (tests, lint rules, codemods) that improve code quality and maintainability.
  • Useful for audits, onboarding, and continuous improvement by surfacing concrete artifacts.

Quick Start

Identify a high-impact area in the Breadboard codebase and produce a concrete artifact (test, lint rule, or codemod).

Frequently Asked Questions about daily-dig

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

FAQPage Schema
What is code quality artifact generation for complex modules with low test coverage?

Code quality artifact generation involves producing tests, lint rules, or codemods when you find defects. It provides a structured exploration workflow to document issues in complex modules with low test coverage.

How do I generate lint rules and tests for code containing TODO or FIXME markers?

Generating lint rules and tests for flagged code areas requires targeting modules containing TODO or FIXME markers. You explore these areas to produce tangible artifacts that improve maintainability.

Can I use codemods to document defects found during a codebase audit?

Yes, you can use codemods to document defects found during a codebase audit. The process yields verifiable artifacts, logging your findings in a Hall of Fame to ensure continuous improvement.

What is the best way to locate defects across complex modules during onboarding?

The best way to locate defects across complex modules during onboarding is to follow a structured exploration workflow. This approach surfaces concrete artifacts from flagged code areas, ensuring verifiable results.