Results for “technical-correctness”

Identify underspecified areas in the current feature spec by asking targeted clarification questions and encoding answers back into the spec.

Identify error-prone APIs and dangerous configurations

Scan codebases for technical debt, score severity, track trends, and generate prioritized remediation plans.

Analyze weekly price charts for stocks, indices, crypto, or forex to identify trends, support/resistance, and probabilistic scenarios based purely on chart data.

Reviews and repairs risky or unclear code with minimal validated changes, running a fixed-point loop until the diff is clean across two consecutive review cycles.

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

Scan codebases for technical debt, score severity, track trends, and generate prioritized remediation plans. Use when users mention tech debt, code quality, refactoring priority, debt scoring, cleanup sprints, or code health assessment. Also use for legacy code modernization planning and maintenance cost estimation.

Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md. Identifying inconsistencies, duplications, ambiguities, and underspecified items.

SSOT（Single Source of Truth）と実際のファイル/設定の整合性をチェックし、乖離があれば修正するスキル。 「SSOTチェックして」「SSOT整合性チェックして」「SSOT整理して」「SSOTのズレを直して」 「00_SYSTEM更新して」「乖離を修正して」と言った時にトリガーする。 /ssot-check でも呼び出せる。

Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.

Verify TPM measured boot integrity and remote attestation using tpm2-tools, including PCR reading, event log replay, quote generation and verification, and golden baseline comparison.

Guides technical evaluation of code review feedback, emphasizing verification before implementation and reasoned pushback over performative agreement.

Write product-facing technical specs that clarify decisions, constraints, dependencies, and rollout.

Internal technical readiness drill assistant for release and handoff.

Diagnose failures from runtime evidence before editing code.

Technical leadership guidance for engineering teams, architecture decisions, and technology strategy. Use when assessing technical debt, scaling engineering teams, evaluating technologies, making architecture decisions, establishing engineering metrics, or when user mentions CTO, tech debt, technical debt, team scaling, architecture decisions, technology evaluation, engineering metrics, DORA metrics, or technology strategy.

Guides technical verification of code review feedback before implementation, emphasizing reasoned pushback over performative agreement.

Guides minimal-diff code changes by defining contracts and invariants, choosing a stable seam, and proving the result with an executed check.

Formally verify programs by writing Lean 4 proofs. Trigger this skill whenever the user wants to formally verify code, generate Lean 4 proofs, prove properties about algorithms or smart contracts, verify invariants, convert program logic into formal specifications, or anything involving Lean 4 and formal verification. Also trigger when the user mentions "qedgen", "lean proof", "formal proof", "verify my code", "prove correctness", "formal verification", or wants mathematical guarantees about their implementation.

Improve unclear UX copy, error messages, microcopy, labels, and instructions to make interfaces easier to understand. Use when the user mentions confusing text, unclear labels, bad error messages, hard-to-follow instructions, or wanting better UX writing.

Improve unclear UX copy, error messages, microcopy, labels, and instructions to make interfaces easier to understand. Use when the user mentions confusing text, unclear labels, bad error messages, hard-to-follow instructions, or wanting better UX writing.