task-completion-standards

Validate ESLint rule development tasks against predefined quality and file standards.

2|1|Updated May 16, 2023
One-click install
npx skills add https://github.com/BluMintInc/eslint-custom-rules --skill task-completion-standards
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: task-completion-standards
Source: https://github.com/BluMintInc/eslint-custom-rules/tree/main/.claude/skills/task-completion-standards
Command: npx skills add https://github.com/BluMintInc/eslint-custom-rules --skill task-completion-standards

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a clear checklist and standards to ensure that ESLint rule development tasks are completed thoroughly and meet the project's quality requirements, preventing common rejections and streamlining the review process.

Core Features & Use Cases

  • Defines "Definition of Done": Clearly outlines the expected files, tests, and quality checks for both new rule implementations and bug fixes.
  • Identifies Common Pitfalls: Highlights frequent reasons for task rejection, such as missing files or insufficient tests.
  • Use Case: A developer is about to submit a new ESLint rule. They consult this Skill to verify they have created the rule file, test file, documentation, updated src/index.ts correctly, and met the minimum test count and linting requirements.

Quick Start

Use the task-completion-standards skill to review the checklist for completing an ESLint rule task.

Frequently Asked Questions about task-completion-standards

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

FAQPage Schema
What is required to complete an ESLint rule development task?

You can identify missing files or insufficient tests by validating against predefined quality standards. This skill highlights frequent reasons for task rejection, such as missing documentation or failing to meet the minimum test count for ESLint rules.

How do I ensure my custom ESLint rule passes project review?

You can identify missing files or insufficient tests by validating against predefined quality standards. This skill highlights frequent reasons for task rejection, such as missing documentation or failing to meet the minimum test count for ESLint rules.

What files need to be updated when creating a new ESLint rule?

When creating a new ESLint rule, you must update the rule file, test file, documentation, and the src/index.ts configuration. These updates ensure the rule is properly integrated and meets the project's development workflow standards.

Why does my ESLint rule task get rejected during code review?

Your ESLint rule task may get rejected due to missing files, insufficient tests, or failing build checks. Validating against task completion standards helps identify these common pitfalls and ensures all quality requirements are met.

Do I need to run linting and build checks before submitting an ESLint rule fix?

Yes, you must run linting and build checks before submitting an ESLint rule fix. Completion standards require comprehensive testing and successful builds to ensure both new implementations and bug fixes meet quality requirements.