Skip to content
Back to skills

Issue Solver

ASecurity

Autonomous engineering agent that reads GitHub issues, traces root causes, designs GRASP-compliant fixes, runs tests, opens PRs, and closes issues only after merge.

  • 18 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added September 6, 2026
ai-agentsgitdatabasesecurityperformance

Works with

  • cli

Security analysis

A100/100

Scanned September 6, 2026

npx -y skills add conectlens/lenserfight --skill issue-solver --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Issue Solver?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Issue Solver
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/conectlens-issue-solver/badge)](https://www.skillsdirectory.com/skills/conectlens-issue-solver)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: issue-solver
description: Autonomous engineering agent that reads GitHub issues, traces root causes, designs GRASP-compliant fixes, runs tests, opens PRs, and closes issues only after merge.
---

# Issue Solver

## Purpose

Use this lenser when you want an autonomous engineering agent to carry a GitHub issue from triage to merged PR, including tests, without manual hand-offs between steps.

## Instructions

- Fetch the issue from GitHub before doing anything else.
- Classify the issue type: bug, feature, security, performance, docs, DX, database, workflow, CLI, mobile, or web.
- Identify root cause before proposing any code. Do not describe symptoms — describe causes.
- Apply GRASP and OOAD principles: Information Expert, Low Coupling, High Cohesion, single source of truth, server-side business rule enforcement.
- Implement the minimal correct fix. No unrelated refactors. No hardcoded temporary fixes. No security bypasses.
- Run tests in ascending scope: single spec → project → affected. Add tests if root cause is uncovered.
- Create a branch, commit with Conventional Commits format, push, open a PR against `development`, and link it to the issue.
- Monitor CI. Fix failures before merging.
- Merge only after all checks pass, no unsafe migrations, no security regressions.
- Synchronize `development` locally after merge and verify the fix is present.
- Close the issue only after merge and post-merge validation pass.

## Execution Policy

The lenser may:
- Read any file in the repository
- Run `gh`, `git`, `pnpm nx`, and `pnpm supabase` commands
- Create branches, commits, and PRs
- Open and close GitHub issues with evidence

The lenser must pause and ask before:
- Force-pushing to any branch
- Dropping or truncating database tables
- Applying irreversible migrations
- Merging when CI is failing
- Closing an issue without a merged PR

## Output Expectations

At each phase, report:
- What was done
- What was found
- What the next step is

Final output: GitHub Issue Solver — Final Report (issue, root cause, solution, PR URL, merge commit, post-merge validation, issue closure status, remaining risks).

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.