More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    AI GitHub Issue-to-PR Builder

    1

    Turn GitHub issues into minimal, verified, review-ready code changes.

    $9.99

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    AI GitHub Issue-to-PR Builder

    AI GitHub Issue-to-PR Builder

    Example session with this skill installed

    Fix GitHub issue #142: Users can submit the registration form with an invalid email address.

    Please inspect the repository first. Identify the relevant validation code and existing tests, determine the smallest safe fix, implement it, add or update regression tests, run the appropriate verification commands, inspect the final diff for unrelated changes, and prepare a review-ready PR summary.

    Do not refactor unrelated code or add new dependencies.

    • Read your context and instructions
    • Compiled the ai github issue-to-pr

    Task Interpretation

    Fix the registration email validation issue reported in #142 without changing unrelated registration behavior.

    Repository Findings

    • Located the registration validation logic in src/....
    • Found existing registration tests in tests/....
    • Confirmed the repository's existing test and lint commands from its project configuration.
    • No new dependency is required.

    Acceptance Criteria

    • Invalid email addresses are rejected.
    • Valid email addresses continue to be accepted.
    • A regression test covers the reported invalid input.
    • No unrelated registration behavior is changed.

    Implementation

    Updated the existing validation boundary and added a focused regression test using the project's existing testing conventions.

    Verification

    • Targeted registration tests: PASS
    • Relevant lint/check: PASS
    • Final diff inspection: PASS
    • No unrelated files or temporary artifacts introduced.

    PR Title

    Fix registration email validation

    PR Summary

    Changes

    • Tightened email validation at the existing registration validation boundary.
    • Added regression coverage for invalid email input.

    Risk

    Low. The change is limited to the reported validation behavior and preserves valid email handling.

    Rollback

    Revert the two changed files if the validation behavior causes an unexpected compatibility issue.

    Reviewer Notes

    The implementation uses the repository's existing validation and testing patterns and avoids introducing a new dependency.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    AI GitHub Issue-to-PR Builder turns GitHub issues, bug reports, feature requests, and repository tasks into disciplined, review-ready implementation workflows.

    It first analyzes the issue and repository, identifies acceptance criteria, inspects relevant code and tests, creates a minimal implementation plan, and only modifies files when implementation is explicitly authorized.

    After implementation, it verifies the change with the project's existing tests and checks, audits the final diff for scope creep and accidental artifacts, and produces a complete PR package with summary, acceptance criteria, verification evidence, risks, rollback guidance, and reviewer notes.

    Designed for cross-agent compatibility with Claude Code, Codex CLI, Cursor, Gemini CLI, GitHub Copilot, and other agents supporting the SKILL.md standard.

    This skill depends on the capabilities of the AI coding agent and the repository it is given. It can analyze local repository files and prepare implementation or PR-ready output, but it cannot create or push a remote GitHub pull request unless the agent has an appropriate GitHub integration or CLI and the user explicitly authorizes that action.

    Test, lint, type-check, and build verification depends on the commands and tooling available in the repository. The skill never claims a check passed unless it was actually run and verified.

    It does not require API keys, external network access, or secret sharing.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 3 months ago

    Permissions

    Read Files
    Write Files
    Listed3 months ago

    What's inside

    Frequently Asked Questions

    It turns a GitHub issue, bug report, or feature request into a disciplined implementation workflow: repository investigation, acceptance criteria, minimal change planning, implementation, verification, diff auditing, and PR-ready documentation.

    Only when implementation is explicitly authorized. Otherwise it operates in plan-only mode.

    No. It can prepare everything needed for a PR. Remote PR creation requires explicit authorization plus an available GitHub integration or CLI.

    Yes, when implementation is authorized and the repository provides appropriate tests or verification commands.

    No. The core skill does not require API keys or external services.

    Yes. It is designed to inspect the repository's actual structure, conventions, configuration, tests, and local instructions before recommending or making changes.

    Yes. It explicitly audits the final diff and flags unrelated changes, unnecessary refactoring, dependency additions, and unexplained modifications.

    New in Testing & Debugging