code-spec-backfill

Backfill missing function contracts and type hints across a codebase.

Updated Mar 5, 2026
One-click install
npx skills add https://github.com/Nathanto-ai/liza-private --skill code-spec-backfill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-spec-backfill
Source: https://github.com/Nathanto-ai/liza-private/tree/main/skills/code-spec-backfill
Command: npx skills add https://github.com/Nathanto-ai/liza-private --skill code-spec-backfill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Backfill missing function contracts (docstrings and type hints) where gaps exist to improve code quality and maintainability. It also reports unresolvable gaps with misuse scenarios to guide incremental improvements.

Core Features & Use Cases

  • Incremental backfill of function contracts and type annotations across a codebase.
  • Report unresolvable gaps with misuse scenarios to drive human review.
  • State-driven workflow that enables gradual, safe improvements.

Quick Start

Run the skill on your repository to backfill missing function contracts and review added docstrings and type annotations.

Frequently Asked Questions about code-spec-backfill

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I backfill missing docstrings and type hints across a large codebase?

To backfill missing docstrings and type hints, you can run an incremental, state-driven workflow that scans your repository and adds explicit function contracts. This enforces precise interfaces across multiple modules and teams.

What is the best way to enforce explicit function contracts without breaking existing code?

Enforcing explicit function contracts is achieved through incremental, non-breaking improvements. A state-driven workflow applies missing docstrings and type hints gradually, ensuring stability while improving codebase maintainability.

Can I identify unresolvable type hint gaps and misuse scenarios in my repository?

Yes, identifying unresolvable type hint gaps is supported. The backfill process reports missing function contracts alongside misuse scenarios, driving targeted human review for complex interface inconsistencies.

How do I add type annotations to public APIs incrementally across multiple teams?

Adding type annotations to public APIs incrementally is handled by a state-driven workflow. This approach tracks backfill progress, enabling safe and gradual improvements across large repositories with multiple contributing teams.

Does this approach work for large repositories with inconsistent public APIs?

Yes, this approach is designed for large repositories with inconsistent or missing public APIs. It backfills function contracts and type hints incrementally, enforcing precise interfaces across disparate modules and teams.

What are the limitations of automatically backfilling function contracts?

The limitation of automatically backfilling function contracts is that unresolvable gaps cannot be fully automated. The process reports these specific gaps with misuse scenarios to guide necessary human review.