Çoklu dosya
codingResmi
Resmi Sağlayıcı Skill'iView repo
Guide for writing effective code documentation, including docstrings, JSDoc, dartdoc, and implementation comments. Use this skill when writing new code, adding features, or improving existing documentation in Dart, Python, or TypeScript to ensure clarity and maintainability.
Dosyalar4 dosya
SKILL.md70 satır
Loading editor…
Kurulum
ÖnerilenTek komut — ajanınız otomatik olarak devreye alır.
Kurulum komutunu görmek için yukarıdan bir AI aracı seçin.
veya
Manuel Kurulum
Daha fazla adımArşivi indirin ve dosyaları projenize manuel olarak ekleyin.
Skill detayları
Versiyonv1.0.0
YazarFlutter
Kategoricoding
Skill IDflutter/agent-plugins/.agents/agents/reidbaker-agent/skills/code-documentation
Dosyalar4 dosya
İlgili skill'ler
Api ReviewReviews the specified code against the canonical API Design guidelines. Use this skill when the user asks for an API review or to check code against API design principles.Code ReviewPerforms a comprehensive, multi-step code review of pull requests or local code changes, using iterative refinement (generation, critique, synthesis) to ensure high-quality, actionable feedback. Use when you need to review code changes thoroughly.Dart Add Unit TestWrite and organize unit tests for functions, methods, and classes using `package:test`. Use when creating new logic or fixing bugs to ensure code remains correct and regression-free.Dart Build Cli AppArchitectural patterns, entrypoint structure, exit codes, stream routing, and subprocess spawning for Dart command-line interface (CLI) applications. Use when building CLI tools, console utilities, scripts, argument parsing with `package:args` (ArgParser or CommandRunner), handling exit codes, configuring executables in pubspec.yaml, spawning Dart subprocesses, or compiling native CLI binaries. Don't use for Flutter UI widgets, web applications, or standalone HTTP backend servers.Dart Collect CoverageCollect coverage using the coverage packge and create an LCOV reportDart Fix Runtime ErrorsUses get_runtime_errors and lsp to fetch an active stack trace, locate the failing line, apply a fix, and verify resolution via hot_reload.