backpack-code-review-checklist

Name: backpack-code-review-checklist
Availability: InStock
Author: Skyscanner

Apply a Backpack component code-review checklist covering API encapsulation, Sass tokens, accessibility, and documentation.

543|211|Updated Mar 22, 2017

Search Tags:#accessibility #components #code-review #design-system #token-usage #backpack

Ready to run

npx skills add https://github.com/Skyscanner/backpack --skill backpack-code-review-checklist

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: backpack-code-review-checklist
Source: https://github.com/Skyscanner/backpack/tree/main/.claude/skills/backpack-code-review-checklist
Command: npx skills add https://github.com/Skyscanner/backpack --skill backpack-code-review-checklist

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a structured, repeatable framework for reviewing Backpack components to ensure compliance with design-system rules, architecture guidelines, and governance processes before merging.

Core Features & Use Cases

Phase-driven checks: constitution compliance, decisions, guidelines, and licensing.
Enforces API encapsulation rules, token usage, and accessibility readiness.
Guides reviewers to document issues and propose concrete fixes.

Quick Start

Run the Backpack Code Review Checklist on the component under test to identify and fix violations before merge.

Frequently Asked Questions about backpack-code-review-checklist

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

FAQPage Schema

How do I review a Backpack design system component for a pull request?▼

To review a Backpack design system component, apply a comprehensive code-review checklist that verifies constitution compliance, API encapsulation, Sass token usage, accessibility tests, and mandatory license headers before merging.

What is the best way to enforce design system token usage and accessibility in code reviews?▼

The best way to enforce design system token usage and accessibility is to apply a phase-driven code review checklist that validates Sass token rules and accessibility readiness, while instructing reviewers to document violations and propose concrete fixes.

Does my Backpack component PR need design approval and test coverage before merging?▼

Yes, your Backpack component PR requires design approvals and must meet specified test coverage thresholds. The code review checklist enforces these mandatory governance processes to ensure component quality and conformance.

How do I document design system violations and recommended fixes during a code review?▼

To document design system violations during a code review, the checklist guides reviewers to explicitly record issues related to API encapsulation, token usage, and accessibility, while proposing concrete fixes for each violation.

What specific architecture guidelines should I check when modifying Backpack components?▼

When modifying Backpack components, check architecture guidelines including API encapsulation rules, Sass token usage, mandatory license headers, constitution compliance, and design system decisions to ensure full architectural conformance.