Results for “checklists”

Enforces a test-first workflow for features and bug fixes, guiding the red-green-refactor cycle with verification checklists.

Provides full-stack development practices covering backend architecture, frontend-backend integration, and production hardening with structured workflows and checklists.

Build Uniswap v4 hooks with security-first guidance on threat modeling, permission flags, NoOp attack prevention, delta accounting, and pre-deployment audit checklists.

Defines quality standards and validation checklists for agent workflows, Python tools, and documentation, including automated checks and pre-commit gates.

Generate a custom checklist for the current feature based on user requirements.

Create punch lists for construction completion inspection. TRIGGERS - Use when user needs help with punch-list related tasks.

Create systematic QA checklists to verify that design implementations match specifications across visual accuracy, layout, interaction, content, accessibility, and cross-platform categories.

Create punch lists for construction completion inspection. TRIGGERS - Use when user needs help with punch-list related tasks.

Conducts structured requirements workshops to produce feature specifications, user stories, EARS-format functional requirements, acceptance criteria, and implementation checklists.

Create bucket lists with categorization and planning. TRIGGERS - Use when user needs help with bucket-list related tasks.

Self-contained code review checklist — formatting, type safety, duplication, readable conditions, logic-out-of-UI, test coverage, comment quality. Adapts to whatever tooling the project actually has (skips Prettier/TypeScript/test-runner checks if unconfigured). Use before merging, after completing a feature, or any time you want a second pass on code quality. In Claude Code, prefer the official `code-review` skill or `pr-review-toolkit`/`feature-dev` code-reviewer agents instead — both are real, installed, and go deeper than this checklist. This copy exists for Codex/Cursor portability, where those agents aren't available.

Build a launch checklist with owners, dates, dependencies, decision gates, and follow-through.

Create bucket lists with categorization and planning. TRIGGERS - Use when user needs help with bucket-list related tasks.

Review local branch changes for bugs, security vulnerabilities, and code quality issues using a structured checklist-driven process.

Selects and reviews Queueable, Batch, Future, and Schedulable Apex for callouts, large data processing, retries, and background work, with decision guidance and validation checklists.

Comprehensive checklist for documenting follow-up work and testing needs after implementation

Brainstorm a longlist of benefits and costs for a project. Outputs two clean tables (benefits and costs), each with materiality (H/M/L), a cash flow tag (cash in / cash out / non-cash), a quantification method, and a monetisation method. Supports HMT Green Book, EU Better Regulation Guidelines, World Bank, Asian Development Bank, and the Victorian Treasury High Value High Risk (HVHR) framework.

Reviews local branch changes for bugs, security vulnerabilities, and code quality issues using a structured checklist and attack surface mapping.

Verify tasks marked [X] in tasks.md are implemented, not phantom completions (marked done but backed by missing or dead code).

Create medical coding guides for billing accuracy. TRIGGERS - Use when user needs help with coding-guide related tasks.

Git-level WIP safety net. Stashes uncommitted work, tags, and pushes to remote

Skill for the Observability area of paddock. 105 symbols across 26 files.

Enforces a principal-engineer self-review checklist on every code block before output, covering correctness, performance, security, naming, and testability.

Provides a structured code review checklist covering security, performance, correctness, maintainability, testing, accessibility, and documentation, with a three-pass review process and guidance on severity levels and anti-patterns.

Provides a comprehensive checklist for designing REST and GraphQL APIs, covering resource design, HTTP methods, status codes, pagination, security, performance, and documentation.

Drafts litigation-ready U.S. pre-suit demand letters that function as settlement instruments and defensible future exhibits. Enforces element-driven narratives, verified authority, damages methodology, and ethics guardrails. Use this skill when the user mentions demand letter, pre-suit demand, breach and cure notice, settlement demand, insurance policy-limits demand, Stowers demand, FDCPA collection letter, notice of intent to file, cease and desist demand for payment, or pre-litigation correspondence. Also trigger when the user asks about FRE 408 framing, contractual notice compliance, statutory pre-suit prerequisites, evidence preservation notices, or quantifying damages for a demand package. Skill includes 14 verified real-letter exemplars referenced from `references/ARCHETYPE-INDEX.md`.

Use when you have a written implementation plan to execute in a separate session with review checkpoints

Checks a GitHub, GitLab, or Perforce (p4) pull request (or merge request, or shelved changelist) for unresolved review comments, failing status checks, and incomplete PR descriptions. Waits for pending checks to complete, categorizes issues as actionable or informational, and optionally fixes and resolves them. Use when the user wants to check a PR/MR/CL, address review feedback, or prepare a change for submission.

Migrate AEM Cloud Service resource listeners to the lightweight ResourceChangeListener + JobConsumer pattern, covering migration from legacy APIs, OSGi configuration, troubleshooting, and review checklists.

Guides migration of AEM Cloud Service schedulers from legacy patterns to OSGi-compliant Sling Scheduler or Sling Jobs, with classification, review checklists, and troubleshooting.