autoreview
المصدرopenclaw/openclaw/.agents/skills/autoreview/SKILL.md
آخر تحديث
Structured Codex, Claude, Amp, Pi, or Kimi code review when explicitly requested.
تصفح مهارات الوكيل
طابق عبارة البحث كاملة وبالترتيب نفسه.
نتائج البحث
ترتيب حسب
13+ نتيجةتطابق النتائج جميع كلمات البحث.
requesting-code-review
المصدرobra/superpowers/skills/requesting-code-review/SKILL.md
آخر تحديث
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
receiving-code-review
المصدرobra/superpowers/skills/receiving-code-review/SKILL.md
آخر تحديث
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
code-review
المصدرmattpocock/skills/skills/engineering/code-review/SKILL.md
آخر تحديث
Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes: Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/spec asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to "review since X".
intent-driven-development
المصدرaffaan-m/ECC/skills/intent-driven-development/SKILL.md
آخر تحديث
Turn ambiguous or high-impact product and engineering changes into scoped, verifiable acceptance criteria before or alongside implementation. Use when a user asks to clarify a feature, define acceptance criteria, de-risk a security/data/migration/integration change, prepare implementation requirements for another agent, or make a complex request testable. Do not trigger for trivial edits, straightforward fixes, active debugging, code review, or implementation requests whose acceptance conditions are already clear unless the user explicitly invokes this skill.
dart-flutter-patterns
المصدرaffaan-m/ECC/skills/dart-flutter-patterns/SKILL.md
آخر تحديث
Production-ready Dart and Flutter patterns covering null safety, immutable state, async composition, widget architecture, popular state management frameworks (BLoC, Riverpod, Provider), GoRouter navigation, Dio networking, Freezed code generation, and clean architecture. Use when writing or reviewing Dart and Flutter code — state, widgets, navigation, networking, or architecture.
orch-refine-code
المصدرaffaan-m/ECC/skills/orch-refine-code/SKILL.md
آخر تحديث
Orchestrate a behavior-preserving refactor — confirm tests are green, restructure without changing behavior, keep tests green, review, and gated commit. Use when the structure should improve but behavior must not change.
flutter-dart-code-review
المصدرaffaan-m/ECC/docs/ja-JP/skills/flutter-dart-code-review/SKILL.md
آخر تحديث
ウィジェットのベストプラクティス、状態管理パターン（BLoC、Riverpod、Provider、GetX、MobX、Signals）、Dartのイディオム、パフォーマンス、アクセシビリティ、セキュリティ、クリーンアーキテクチャをカバーするライブラリに依存しないFlutter/Dartのコードレビューチェックリスト。
repo-scan
المصدرaffaan-m/ECC/skills/repo-scan/SKILL.md
آخر تحديث
Bootstrap pointer that installs the external repo-scan skill from a pinned, reviewable commit. Use when repo-scan must be installed before running its cross-stack source-code asset audit; this ECC pointer does not perform the audit itself.
perl-patterns
المصدرaffaan-m/ECC/skills/perl-patterns/SKILL.md
آخر تحديث
Modern Perl 5.36+ idioms, best practices, and conventions for building robust, maintainable Perl applications. Use when writing or reviewing modern Perl 5.36+ code.
coding-standards
المصدرaffaan-m/ECC/skills/coding-standards/SKILL.md
آخر تحديث
Baseline cross-project coding conventions for naming, readability, immutability, and code-quality review. Use detailed frontend or backend skills for framework-specific patterns. Use when reviewing code quality or naming with no framework-specific skill that applies.
cpp-coding-standards
المصدرaffaan-m/ECC/.kiro/skills/cpp-coding-standards/SKILL.md
آخر تحديث
C++ coding standards based on the C++ Core Guidelines (isocpp.github.io). Use when writing, reviewing, or refactoring C++ code to enforce modern, safe, and idiomatic practices.