OpenHands/extensions - Page 3

release-notes

Generate formatted changelogs from git history since the last release tag. Use when preparing release notes that categorize changes into breaking changes, features, fixes, and other sections.

improve-agent-readiness

Use an agent readiness report to identify and implement improvements that make a repository more agent-friendly. Proposes repo-appropriate fixes for each pillar, then implements them on request. Use after running a readiness report or when a user wants to…

setup-agents-md

Generate a high-quality, repo-specific AGENTS.md file that tells AI agents how to work effectively in a repository. Reads the actual repo to extract commands, structure, conventions, and guardrails — never generates generic boilerplate. Use when a user wants…

setup-openhands

Set up a repository for effective use with OpenHands. Creates AGENTS.md, setup and pre-commit scripts, and a PR review workflow. Designed to run automatically with minimal user intervention. Use when a user wants to configure their repo for OpenHands.

setup-pr-review

Set up the OpenHands automated PR review workflow in a GitHub repository. Creates the workflow file and asks the user for configuration preferences. Use when a user wants AI code review on their pull requests.

mainframe-planning

Create a transformation guide for replacing mainframe-specific COBOL constructs with standard COBOL equivalents. Use when preparing COBOL code for local execution or migration.

to-java-migration

Migrate COBOL code to idiomatic Java, preserving business logic while following Java best practices. Use for COBOL modernization projects.

migration-mapping

Create a mapping from source language files to target language files for code migrations. Use when evaluating or documenting a migration project.

migration-report

Generate a comprehensive migration report summarizing quality scores and providing recommendations. Use after scoring a migration project.

score-quality

Score code migration quality based on coverage and correctness. Evaluates how well target code represents source functionality.

score-style

Score migrated code against style guidelines and best practices. Evaluates code quality independent of functional correctness.