implement-type-annotations

This skill focuses on enhancing software quality and developer productivity by systematically applying comprehensive type annotations to Python and TypeScript codebases. By enforcing type safety through PEP 484-compliant type hints in Python and robust interfaces or types in TypeScript, this agentic skill helps developers catch runtime errors during the static analysis phase, significantly reducing debugging time and improving overall system reliability. It is specifically designed for software engineers, repository maintainers, and DevOps teams who are looking to modernize their codebase to better support AI-assisted development tools, which rely on explicit type information to generate more accurate and context-aware code suggestions.

• Increases IDE intellisense accuracy by providing clear visibility into function signatures, expected argument types, and return values.

• Automates the identification and remediation of missing type annotations in legacy code segments.

• Improves AI-assisted development (such as GitHub Copilot or Claude) by providing the structural context required for high-fidelity code completion.

• Enforces consistency across the repository, ensuring that type hints are applied uniformly throughout the project lifecycle.

• Facilitates earlier bug detection by enabling tools like Mypy, Pyright, or the TypeScript compiler to catch type mismatches before execution.

• Usage: Apply this skill during the refactoring or maintenance phase of a software development project to stabilize the codebase.

• Inputs: Targets specific directories or individual files containing Python (.py) or TypeScript (.ts, .tsx) source code.

• Outputs: Generates updated source files with appropriate type annotations, potentially accompanied by summary reports on type coverage percentages.

• Constraints: Users should have a standard linting and type-checking infrastructure in place, such as Mypy for Python or Tsc for TypeScript, to verify the agent's changes.

• Integration: Ideally used in conjunction with CI/CD pipelines to monitor type coverage as a quality metric, preventing regressions in type safety over time.