1k-retrospective
Retrospective: Evolve Self-Testing Rules from Real Cases
Workflow
Step 1: Read Cases
Read .claude/skills/1k-retrospective/references/case-studies.md. Count cases since the last <!-- Retrospective completed --> marker. If fewer than 3 new cases, report "Not enough new cases" and stop.
Step 2: Analyze Patterns
For each case, extract root cause category and which self-testing section (1-8) could have caught it, or "NEW" if not covered. Aggregate counts per pattern.
Step 3: Identify Gaps and Weak Spots
- Gaps: patterns appearing 2+ times marked "NEW" → candidates for new check items
- Weak spots: patterns appearing 3+ times already covered → check item needs stronger wording or more specificity
Step 4: Propose Changes
More from onekeyhq/app-monorepo
react-best-practices
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
109implementing-figma-designs
Implements Figma designs 1:1 using OneKey component library (还原设计稿).
771k-coding-patterns
Coding patterns and best practices — React components, promise handling, and TypeScript conventions.
691k-code-quality
Code quality standards — lint (eslint/oxlint), type check (tsc), pre-commit hooks, and comment conventions. All comments must be in English.
681k-date-formatting
Date and time formatting — use OneKey dateUtils (formatDate/formatTime) instead of native JS date methods.
681k-git-workflow
Git workflow and conventions — branching, commit messages, and PR creation.
68