perform-task-end-to-end

Executes bugfix and feature tasks end-to-end with checklists, tests, and PR creation.

649|197|Updated Jan 28, 2020
One-click install
npx skills add https://github.com/razorpay/blade --skill perform-task-end-to-end
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: perform-task-end-to-end
Source: https://github.com/razorpay/blade/tree/main/.agents/skills/perform-task-end-to-end
Command: npx skills add https://github.com/razorpay/blade --skill perform-task-end-to-end

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Engineering tasks often get marked done before tests, linting, typechecks, and PR readiness are verified, leading to broken builds and incomplete features. This Skill enforces a structured end-to-end workflow so every bugfix or feature in the Blade Design System is fully implemented, tested, and review-ready.

Core Features & Use Cases

  • Task Classification: Categorizes incoming work as bugfix, feature, or other, then applies the appropriate checklist.
  • Bugfix Workflow: Guides debugging, fixing, adding regression tests, and creating Storybook stories for visual bugs.
  • Feature Workflow: Breaks large features into subtasks, adds stories and tests, and verifies implementation.
  • Code Sanity Checklist: Runs browser verification, Prettier, tests, lint, build, and typecheck on changed files, iterating until all pass.
  • Use Case: A developer asks the agent to fix a broken Button component hover state. The Skill walks through reproducing the bug, fixing it, adding a regression test and story, running all sanity checks, adding a changeset, and opening a ready-for-review PR.

Quick Start

Ask the agent to perform a bugfix or feature task end-to-end in the Blade repository, such as fixing a component bug and opening a ready-for-review PR.

Frequently Asked Questions about perform-task-end-to-end

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

FAQPage Schema
How do I complete a bugfix end-to-end in a design system repository?

Debug and identify the root cause, apply the fix, add a regression test, and create a Storybook story for visual bugs. Then run Prettier, tests, lint, build, and typecheck on changed files, add a changeset, and open a ready-for-review PR.

How do I break down a large feature request into subtasks?

Classify the request as a feature task, then split it into smaller subtasks added to the checklist. For each part, add a Storybook story, write unit tests, and verify the code sanity checklist before creating the PR.

What checks should run before marking a frontend task as done?

Run Prettier formatting, unit tests, linting, build, and typecheck on the changed files, plus browser-based UI verification of the story. Fix any failures iteratively and add a changeset with the correct semver bump.

When should a Storybook story be added for a bugfix?

Add a Storybook story when the bug is visual or functional in nature, so the fixed behavior can be verified in the browser. Purely internal logic fixes may not require a story.

Why should a PR be created in ready-for-review state instead of draft?

A ready-for-review PR signals the task is fully complete with all checks passing, tests added, and a changeset included. Draft PRs indicate unfinished work, which this end-to-end workflow is designed to avoid.