More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    first pr finder

    1

    Pre-flight GitHub issue analysis to detect conflicts, verify actionability, and map technical implementation risks.

    Free

    Security scanned
    first pr finder

    first pr finder

    Example session with this skill installed

    Analyze issue #442 in the current repository. Check if it's still actionable and give me a minimal implementation plan if it is.

    • Read your context and instructions
    • Compiled the first pr finder

    I have completed the pre-flight analysis for issue #442. I searched pull requests, commit history, and recent comments to verify the status.

    Pre-flight Analysis Report: Issue #442

    CategoryStatusEvidence
    Issue VerdictAVAILABLENo active PRs or ownership claims found in the last 6 months.
    ClarityVERIFIEDRequirements for the new logger middleware are explicitly defined.
    Code EvidencePARTIALTarget directory src/middleware/ exists; entry point identified.
    TestabilityVERIFIEDExisting suite found in tests/middleware/; npm test is the command.
    Conflicting WorkNONEChecked 30 recent PRs; no overlapping changes to logging logic.

    Technical Impact & File Map

    • src/middleware/logger.ts: TOUCH (Add middleware implementation)
    • src/index.ts: TOUCH (Register new middleware in the pipeline)
    • package.json: DON'T-TOUCH (No new dependencies required)
    • tests/middleware/logger.test.ts: TOUCH (Add unit tests for error levels)

    Risk Register

    • Regression: Low. New middleware is additive and does not modify existing handlers.
    • Compatibility: No breaking changes to the Request object identified.
    • Unknowns: Maintainer preference for specific log formats is not in CONTRIBUTING.md.

    Next steps

    1. Review the src/middleware/ directory to match the existing handler pattern.
    2. Run npm test to establish a baseline before modifying src/index.ts.
    3. Post a comment on #442 referencing this plan to signal intent to maintainers.

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

    About this skill

    Software contributions often fail because developers overlook existing work, stale issues, or maintainer conventions. This skill provides a read-only pre-flight intelligence layer to evaluate GitHub issues before you write a single line of code. It prevents wasted effort by detecting competing pull requests, ownership claims, and hidden technical risks.

    What it does

    • Issue validation determines if a task is still actionable, already resolved, or previously rejected.
    • Conflict detection scans for active work, ownership claims, and unmerged pull requests.
    • Dependency mapping identifies code paths, call sites, and potential regression risks.
    • Readiness scoring evaluates issues based on clarity, testability, and repository compliance.
    • Implementation planning generates a minimal file-change map and evidence-backed technical approach.

    How it works

    1. Target Identification: Provide a GitHub URL, issue number, or local repository context to begin the scan.
    2. Pre-flight Audit: The agent checks authenticated tools and search history for ownership signals and competing work.
    3. Intelligence Report: Receive a categorized verdict like AVAILABLE or ACTIVE_WORK alongside a risk register.
    4. Implementation Scaffolding: Review the suggested code-path analysis and test commands discovered from the source.

    Frameworks & tools

    This tool works with GitHub via CLI or API and handles any language or framework by inspecting README.md, CONTRIBUTING.md, and CI configurations.

    Why this beats prompting it yourself

    Generic prompts often ignore the "human" metadata of open source, like abandoned PRs or maintainer feedback in old comments. This skill enforces a specific evidence-backed workflow that treats issue status as a hard gate before suggesting changes.

    Use cases

    • OSS triage to find high-signal issues for new contributors.
    • Pre-sprint audit to ensure internal team tasks aren't already being addressed elsewhere.
    • Risk assessment for complex refactors to map out the blast radius before starting work.

    Known limitations

    GitHub access depends on your environment's authentication. Static analysis may miss dynamic loading or external consumers. Status verdicts are evidence-based interpretations, not maintainer guarantees.

    CREDITS :)

    Access requires authenticated tools. Search coverage may be limited by API rate limits. Static analysis excludes dynamic loading or external services. Signals are evidence, not binding intent.

    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

    Free forever

    No account required to browse

    Trust & safety

    Security scan

    Security scan passed 20 days ago

    • Free with an Agensi account

    Requires

    GitHub
    Node.js
    macOS

    Permissions

    Read Files
    Write Files
    Terminal / Shell
    Browser
    Network Access

    Allowed Hosts

    api.github.com

    Before giving the Prompt just mention to use the skill

    Listed20 days ago

    What's inside

    Frequently Asked Questions

    This skill identifies 'hidden' blockers such as abandoned pull requests, stale ownership claims, and maintainer feedback in old comments that standard AI prompts usually miss, ensuring you don't waste time on issues that won't be merged.

    The skill works with any GitHub-hosted repository regardless of language, as it dynamically inspects your specific project's CONTRIBUTING guidelines, CI configs, and file structure to provide context-aware advice.

    You will receive the structured agent skill package designed for immediate deployment, including the logic for issue validation, conflict detection, and implementation risk mapping.

    You will need GitHub CLI (gh) or API access configured in your agent's environment; the skill uses your existing authentication to perform its read-only scans and intelligence gathering.

    No, the skill operates in a strictly read-only mode to analyze history and code paths, ensuring it never makes unauthorized comments or commits to your repositories.

    New in APIs & Backend