More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    GitHub Issue-to-Pull-Request Agent

    1

    Converts GitHub issues into repository-aware implementation plans, code changes, tests, and review-ready pull requests.

    $7.99

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    GitHub Issue-to-Pull-Request Agent

    GitHub Issue-to-Pull-Request Agent

    Example session with this skill installed

    Analyze issue #42 regarding duplicate webhook delivery and prepare a full implementation plan and code changes for the fix.

    • Read your context and instructions
    • Compiled the github issue-to-pull-request agent

    Implementation Plan

    1. Move idempotency lookup before delivery creation in webhook_service.py.
    2. Add regression test in tests/test_webhooks.py.
    3. Update CHANGELOG.md.

    Code Changes

    
    # snippet of fix...
    

    PR Description

    Closes #42. Fixes race condition in...

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

    About this skill

    The problem

    GitHub issues are often implementation-ready. Developers waste time interpreting ambiguous requirements, rediscovering repository patterns, and writing repetitive PR descriptions instead of focusing on code.

    What it does

    • Extracts acceptance criteria and behavior models from GitHub issues and comments.
    • Performs repository reconnaissance to identify impacted files and local coding conventions.
    • Generates targeted code changes and automated tests that follow existing architecture.
    • Performs multi-layered verification including security, privacy, and accessibility reviews.
    • Produces complete pull request packages with titles, descriptions, and reviewer guidance.

    Frameworks & tools

    Works with GitHub, Cursor, Claude Code, and Copilot. Supports JavaScript, TypeScript, Python, Go, Rust, Java, Swift, Ruby, SQL, Terraform, and Docker.

    Why this beats prompting it yourself

    Standard prompts often result in scope creep, unrelated refactoring, or tests that validate implementation instead of behavior. This skill enforces a disciplined sequence from requirement modeling to evidence-based verification, ensuring minimal diffs and review-ready outputs.

    Use cases

    • Convert vague bug reports into reproducible test cases and verified fixes.
    • Decompose large, complex issues into manageable, sequenced pull requests.
    • Generate comprehensive API or UI feature implementations with migration notes.
    • Audit existing diffs against original issue requirements for compliance.

    Known limitations

    Cannot independently guarantee deployment safety without repository access and executed CI evidence. High-impact architectural or security decisions require manual specialist approval.

    Requires repository access for reconnaissance. Cannot bypass branch protections or finalize merges without human review. High-risk migrations require manual verification.

    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

    Write Files
    Read Files
    Browser

    File Scopes

    *.md
    *.txt
    *.json
    *.yaml
    *.yml
    *.toml
    *.ini
    *.cfg
    *.xml
    *.html
    *.css
    *.scss
    *.sass
    *.less
    *.js
    *.jsx
    *.ts
    *.tsx
    *.vue
    *.svelte
    *.py
    *.rb
    *.php
    *.java
    *.kt
    *.kts
    *.swift
    *.m
    *.mm
    *.cs
    *.go
    *.rs
    *.c
    *.h
    *.cpp
    *.hpp
    *.dart
    *.sql
    *.sh
    *.ps1
    *.tf
    *.tfvars
    Dockerfile
    Makefile
    README.md
    CONTRIBUTING.md
    CHANGELOG.md
    CODEOWNERS
    .github/**
    src/**
    app/**
    apps/**
    packages/**
    lib/**
    server/**
    client/**
    api/**
    web/**
    mobile/**
    components/**
    services/**
    models/**
    controllers/**
    routes/**
    repositories/**
    utils/**
    hooks/**
    config/**
    database/**
    migrations/**
    schema/**
    tests/**
    test/**
    spec/**
    fixtures/**
    mocks/**
    e2e/**
    docs/**
    scripts/**
    infrastructure/**
    k8s/**
    terraform/**
    ci/**
    workflows/**
    release/**

    This skill uses file access to inspect GitHub issues, issue comments, source code, tests, package manifests, lock files, build files, configuration, schemas, migrations, API definitions, documentation, contribution guides, CODEOWNERS files, CI workflows, pull-request templates, commit conventions, architecture notes, product requirements, logs, stack traces, screenshots, performance reports, accessibility requirements, security requirements, support tickets, incident reports, and existing diffs. It uses write access to create or modify implementation files, test files, fixtures, mocks, configuration, documentation, migration files, changelog entries, implementation plans, verification records, commit summaries, reviewer notes, pull-request descriptions, risk assessments, rollback guidance, and follow-up issue specifications. Browser access is useful when the host environment permits authorized GitHub repository access, issue and pull-request review, current dependency-documentation review, framework-documentation validation, public API documentation research, security-advisory review, standards research, or compatibility validation. The skill should clearly distinguish: Verified Requirement: Explicitly supported by the issue, an authorized maintainer decision, an approved specification, or current repository behavior. Repository Evidence: Confirmed through inspected source code, tests, configuration, schema, documentation, or repository conventions. Assumption: A provisional interpretation that is not yet confirmed. Recommended: A proposed implementation, test, migration, rollout, or review approach based on available evidence. Open Question: A missing decision that affects correctness, scope, security, privacy, compatibility, architecture, accessibility, performance, migration, billing, or user behavior. Executed Verification: A command or check that was actually run and has recorded evidence. Not Run: A validation step that was identified but not executed. Blocked: A step that could not be completed because of missing access, dependencies, environment, evidence, or approval. The agent must never invent repository files, API contracts, database constraints, environment variables, test results, command output, CI results, deployment outcomes, or pull-request readiness. The agent must never expose or hard-code passwords, tokens, private keys, credentials, customer data, private production records, or internal secrets. The agent should preserve existing architecture and repository conventions unless the issue explicitly requires a justified change. The agent should implement only the verified issue requirements and the minimum supporting changes required for correctness, testability, maintainability, compatibility, and documentation. Generated files should not be edited directly when repository instructions require modifying the source definition and regenerating the output. Baseline test failures must be distinguished from failures introduced by the proposed change. A pull request should not be described as merge-ready when required validation, review, migration analysis, or security approval is missing. Use fictional, anonymized, masked, or approved data in public examples, tests, fixtures, documentation, and screenshots.

    Listed3 months ago

    What's inside

    Frequently Asked Questions

    This skill acts as an end-to-end bridge between an issue description and a merged PR, handling requirement analysis, repository-specific code generation, unit testing, and the final PR documentation automatically.

    The skill is designed for seamless integration with GitHub and is compatible with major AI coding environments including Cursor, Claude Code, and GitHub Copilot.

    Upon purchase, you receive the agent skill configuration, a detailed integration guide for your preferred environment, and lifetime access to version updates and performance improvements.

    The agent performs 'repository reconnaissance' to understand your specific file structure and coding conventions, ensuring all generated code and tests align with your existing architecture.

    While it excels at feature implementation and bug fixes, it cannot independently guarantee deployment safety or make high-level architectural decisions without human oversight.

    Updates are delivered through the marketplace platform, ensuring you always have access to the latest optimizations for new language features and updated AI model capabilities.

    New in Testing & Debugging