Coding & Dev Tools

Speckit Implement

Skill for the Adapters area of paddock. 108 symbols across 22 files.

Comprehensive code review using specialized agents — orchestrates code, comments, tests, errors, types, and simplify agents sequentially.

Perform a non-destructive post-implementation verification gate validating the implementation against spec.md, plan.md, tasks.md, and constitution.md.

Post-implementation quality gate that reviews changes, fixes small issues (scout rule), creates tasks for medium issues, and generates analysis for large issues.

Create a feature branch with sequential or timestamp numbering

General code quality review — project guideline compliance, bug detection, code quality analysis.

Create or update the project constitution from interactive or provided principle inputs, ensuring all dependent templates stay in sync.

Run a full project health diagnostic — checks structure, agents, features, scripts, extensions, and git status.

Validate current branch follows feature branch naming conventions

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

Use when the user needs to run GitNexus CLI commands like analyze/index a repo, check status, clean the index, generate a wiki, or list indexed repos. Examples: "Index this repo", "Reanalyze the codebase", "Generate a wiki"

Error handling review — silent failure detection, catch block analysis, error logging.

Initialize a Git repository with an initial commit

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

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

Use when the user is debugging a bug, tracing an error, or asking why something fails. Examples: "Why is X failing?", "Where does this error come from?", "Trace this bug"

Use when the user asks how code works, wants to understand architecture, trace execution flows, or explore unfamiliar parts of the codebase. Examples: "How does X work?", "What calls this function?", "Show me the auth flow"

Perform a post-implementation retrospective analysis measuring spec adherence, implementation deviations, and lessons learned.

Use when the user wants to know what will break if they change something, or needs safety analysis before editing code. Examples: "Is it safe to change X?", "What depends on this?", "What will break?"

Applies Go rules for packages, explicit errors, interfaces, concurrency, tests, and tooling.

Applies C/C++ rules for resource safety, ownership, ABI, builds, tests, and validation.

Applies ESP32 rules for GPIO, boot states, relays, sensors, connectivity, firmware safety, and validation.

Applies TypeScript/JavaScript rules for types, async behavior, APIs, tooling, tests, and architecture.

Improves structure without behavior changes, using tests and focused slices; not for features unless behavior change is explicit.

Applies practical test-first and regression testing to behavior changes, bug fixes, state transitions, and public contracts.

Applies safe Home Assistant rules for automations, templates, integrations, entity behavior, startup states, and validation.

Maps domains, ownership, dependencies, entry points, tests, services, and risks before broad changes, review, migration, or handoff.

Use only when simplicity, assumption checks, dead-code avoidance, or overengineering resistance is requested. Do not use by default.

Validates rendered UI with browser or Playwright screenshots after implementation, redesign, responsive changes, or visual regressions.

Guides module boundaries, dependency direction, and domain structure. Do not use for local edits that leave architecture unchanged.

Checks desktop, tablet, and mobile UI for overflow, clipping, navigation, grid, canvas, and breakpoint regressions.

Reviews parsers, deserialization, uploads, archives, YAML/JSON/XML/pickle, paths, templates, SSRF, and unsafe loaders.

Grilling

在要求写结构化的 spec、规格文档、行为规格或验收标准时使用。

对一个软件项目或源码仓库进行全面调研，输出一份结构化的中文调研报告，让对项目不熟悉的人能够同时理解"它做什么"和"它怎么实现"。当用户说"调研这个项目 / 分析这个代码库 / 给我一份项目分析报告 / 我要全面理解这个项目 / 帮我看看这个仓库 / onboarding 一下 / 这个项目的整体架构是什么 / 给我梳理下这个源码"等等，或者把一个不熟悉的代码目录交给你并希望你给出全局认识时，必须使用本 skill。即使用户没有显式说"调研报告"，只要意图是"帮我搞懂一个完整的代码库 / 项目"，就应当触发。但本 skill 仅针对"全局理解 / 架构调研 / onboarding"场景：若用户只是要做 code review、定位某个 bug、评审某处具体实现、做性能或安全诊断，不要触发本 skill。