all publishers

pekral

@pekral source repo

88 published skills

  1. ▌
    Auto Interactive Testing · pekral bundle
    Use when every open GitHub issue labelled interactive-testing must be worked through as one unattended batch. Fixes and merges the defects the issues already link, runs each issue's scenarios with the interactive-testing skill on the freshly pulled default branch, resolves and merges every new defect it finds, re-tests, cleans up its test data, then posts the verdicts on each issue and closes it when every scenario passed.
    11 repo stars
  2. ▌
    Machine Payments Protocol · pekral bundle
    Use when implementing, designing, or reviewing the Machine Payments Protocol (MPP) HTTP 402 payment flow in a Laravel/PHP application — middleware placement, payment verification, provider abstraction, pricing, and MCP tool billing. Separates protocol-normative behavior (cited from the IETF draft and its reference implementations) from illustrative naming and generic API-security hardening.
    11 repo stars
  3. ▌
    Create Missing Tests In Pr 2 · pekral
    Use when a PR review already exists and its missing tests must be completed. Reads the pull request code review, verifies which recommended behaviours are already protected, adds only the tests for a missing behavioural contract using the create-test skill, and verifies 100% coverage of the changed code.
    11 repo stars
  4. ▌
    Git History Exposure Audit · pekral bundle
    Use when the user explicitly asks what the git history and the GitHub texts of a repository still expose, and in review mode inside every code review of a project whose GitHub repository is public. A deterministic scan reads every commit, ref, tag annotation, identity, and GitHub text, or the commits a pull request adds, and prints redacted findings: credentials, sensitive files, infrastructure details, identities, and user-supplied terms. Read-only and defensive: it never shows a found value, never tries a credential, never rewrites history, and never publishes the full-audit report.
    11 repo stars
  5. ▌
    Laravel Architecture Guard · pekral
    Use when a Laravel project's layering (Action → ModelService → Repository / ModelManager, or the project's own layers) must be enforced by a test instead of review. Proposes and writes architecture tests that fail when a layer rule is broken, starting from the rules the project already states.
    11 repo stars
  6. ▌
    Test Assignment · pekral bundle
    Use when a task's pull request must be tested against its assignment and the test must prove that nothing else broke. Maps every input that reaches the changed behaviour, builds a test matrix of real data, runs the whole test suite and CI on the final head, and exercises the running application against the base branch. Report mode changes nothing and publishes a test report; fix mode adds the missing tests and fixes, then prepares the pull request for merge without merging.
    11 repo stars
  7. ▌
    Composer Update Pr · pekral bundle
    Use when the user wants to update the Composer dependencies of a project. Switches to the default branch, cleans up integrated local branches, runs composer install, update, and bump, and opens a Draft pull request whose description is a TL;DR of the package updates, read only from the composer.lock and composer.json diff.
    11 repo stars
  8. ▌
    Web Article Writer · pekral
    Use when writing, rewriting, or adapting a publication-ready article for a website or blog. Matches the site's editorial conventions, verifies factual claims, applies restrained on-page SEO, and can prepare an optional illustration brief.
    11 repo stars
  9. ▌
    Github Issue Triage · pekral bundle
    Use when GitHub issues must be prioritized, sorted, or labelled by type, when the open backlog must be swept — issues already merged closed, epics kept flat, issues re-parented under the epic that owns them — when a new issue must be checked against the code — already implemented, reproducible, or missing detail the reporter must supply — or when the issues labelled `analyze` must be analysed and the analysis published on them. Seeds the priority and type label taxonomy and assigns the derived priority to every open issue, so work can be filtered and picked in priority order.
    11 repo stars
  10. ▌
    Interactive Testing · pekral bundle
    Use when verifying user-visible project changes against an assignment and the actual code diff. Requires the testing agent's own interactive browser, checks security risks, verifies suspected vulnerabilities, and reports confirmed threats, which it repairs and re-tests only when the caller explicitly asks for repairs.
    11 repo stars
  11. ▌
    Merge Github Pr Fast · pekral bundle
    Use when the user explicitly invokes /merge-github-pr-fast (Claude Code) or $merge-github-pr-fast (Codex) to land a hotfix pull request on the default branch as soon as possible. Runs one inline security-only check of the diff, then merges when CI on the head commit is green, or when the project's pre-merge quality gate passed on that exact head commit in this run. Needs no converged code review and no approval, promotes a Draft, never uses --admin, and lists every skipped merge-github-pr gate.
    11 repo stars
  12. ▌
    Simplification Audit · pekral bundle
    Use when the user explicitly asks for an audit of the codebase or to refactor a part of the codebase, or in `MODE=cr` over the current diff of every code review. Coordinates a bounded, read-only pass over every subsystem in scope and returns ranked simplification recommendations for data structures, state representation, control flow, algorithms, and ownership, without changing a single file.
    11 repo stars
  13. ▌
    Analyze Support Issue · pekral bundle
    Use when a JIRA issue from a support team needs an analysis a non-technical colleague can act on. Decides whether it is an application bug, a known bug, correct behaviour the user did not expect (with or without a documentation article), a documentation error, a missing feature, a data request, or something outside the application, and publishes one plain-language TL;DR comment in the language of the issue. Runs unattended; every statement in the comment is verified in this run and nothing is estimated.
    11 repo stars
  14. ▌
    Blast Radius Analysis · pekral
    Use when a planned code change must be mapped to everything that depends on it before implementation starts. Produces a read-only, evidence-graded impact report — affected components, risks, unknowns, a targeted verification plan, and implementation constraints — at a depth set by the FAST / STANDARD / CRITICAL tier.
    11 repo stars
  15. ▌
    Deliver Page Redesign · pekral
    Use when one page of a running application must be redesigned end to end from its URL — analysed, proposed with a preview of every state, refined until the user approves the previews, then implemented with the existing design system, reviewed, and verified in a real interactive browser before the pull request is reported.
    11 repo stars
  16. ▌
    Github Release Roadmap · pekral bundle
    Use when planning a GitHub release roadmap for one repository — enumerates issues, labels, milestones, releases, and Projects with `gh`, proposes a versioned release scope for explicit approval, then applies the confirmed plan idempotently without publishing a release or pushing code.
    11 repo stars
  17. ▌
    Verify Merge Readiness · pekral bundle
    Use when a GitHub issue, a GitHub pull request, or a JIRA issue must have its pull request brought to a merge-ready state without merging, then summarized in one source-issue TL;DR while superseded preparation comments are removed safely.
    11 repo stars
  18. ▌
    Do It · pekral bundle
    Use when free-form instructions with several tasks must become a prioritised work queue and be executed end to end. Splits the instructions into independently deliverable items, reuses an existing issue of a trusted author for an item that has one and creates one GitHub issue for every other item, orders the queue by priority, difficulty, and duration, plans parallel batches with plan-parallel.sh, runs every item to a converged pull request through the root-session batch mechanism of batch-preparation.md, and reports each item with its pull request, status, and blocker.
    11 repo stars
  19. ▌
    Test Audit · pekral bundle
    Use when a test is about to be written or changed, when a diff that touches tests is reviewed, or when tests must be audited for low value. Holds the single test-value bar — behaviour, risk, or contract first, coverage only as verification — with a lightweight authoring gate, a read-only code-review lens, a diff mode the implementer runs before the pull request to delete tests that prove no assignment logic while keeping 100% coverage, and an explicit read-only audit of a named scope that proposes KEEP / CONSOLIDATE / MOVE / DELETE with evidence.
    11 repo stars
  20. ▌
    Agent Voice · pekral bundle
    Use when an agent or a skill writes prose that a human reads: a chat reply, the final report to the user, or a comment published to an issue tracker for people to read. Owns the one voice of that prose: the default relaxed voice or the technical voice, selected by the project manifest key voice and overridden by the user's own instruction in the session.
    11 repo stars
  21. ▌
    Create Test 2 · pekral
    Use when creating or updating tests for current changes. Writes the minimum tests that protect the changed behaviour, risk, or contract at its owner boundary, then verifies full coverage of the changed code.
    11 repo stars
  22. ▌
    Git Workflow 2 · pekral
    Use when choosing a Git branching strategy or handling merge vs rebase, conflicts, undoing mistakes, and release tagging — complementing the commit/PR conventions in the git rules.
    11 repo stars
  23. ▌
    Page Redesign · pekral bundle
    Use when an existing application page must be redesigned so its element layout is logical, intuitive, and readable for operators who are not IT people — warehouse, workshop, and shop-floor staff who use the software to process orders as fast as possible. Produces a grounded redesign proposal, a rendered preview screenshot of every state the main view hides, and an implementation-ready handoff a developer can build from without asking a follow-up question. Never changes the application's main layout shell unless the caller explicitly orders it.
    11 repo stars
  24. ▌
    Diagram Design · pekral bundle
    Use when a change, analysis, or document needs a diagram — architecture, request flow, sequence, state machine, ER model, timeline, or comparison — and a picture explains it better than prose. Produces one self-contained HTML + inline SVG file with no build step, no external asset, and no runtime dependency, styled by a fixed editorial design system and validated against a density, contrast, and geometry checklist before it ships.
    11 repo stars
  25. ▌
    Security Audit · pekral bundle
    Use when the user explicitly asks for a security audit of the whole repository or of one subsystem, and in Diff mode over the current diff of every code review. Runs a budgeted, reproducible, coverage-driven audit in the quick, standard, or deep profile: a coverage inventory before hunting, read-only hunters in waves, a fresh coverage critic after each wave, and a new independent verifier for every candidate. Writes metadata.json, coverage-ledger.json, findings.json, and REPORT.md, and validates the JSON against its schemas. An incremental run compares an earlier run with the git diff and reuses its coverage only where the bytes of the security path are unchanged.
    11 repo stars
  26. ▌
    SEO · pekral
    Use when auditing, planning, or implementing SEO in a Laravel app — crawlability, indexability, JSON-LD structured data in Blade, Core Web Vitals, on-page tags, keyword mapping, competitor gap analysis, E-E-A-T content quality, and measurement.
    11 repo stars
  27. ▌
    Benchmark · pekral
    Use when measuring performance baselines or detecting regressions before and after a change in a Laravel app — page Core Web Vitals, API latency percentiles, build/test velocity, and DB query timing, stored as git-tracked baselines for team comparison.
    11 repo stars
  28. ▌
    Blueprint · pekral
    Use when a single objective is too large for one pull request and must span multiple sessions or PRs. Turns the objective into a sequenced construction plan of 3-12 one-PR steps, each with a cold-start context brief, dependency edges, and exit criteria, then reviews it adversarially and registers it as Markdown.
    11 repo stars
  29. ▌
    API Review · pekral bundle
    Use when reviewing HTTP API design in a PR or change set — endpoints, routes, HTTP methods, status codes, idempotency, and input validation. Treats the API as a consumer-facing contract and flags resource-orientation, method-semantics, status-code, and trust-boundary violations. Read-only.
    11 repo stars
  30. ▌
    Pr Summary · pekral bundle
    Use when summarizing current PR changes for the development and product team. Analyzes all commits in the current branch, explains the purpose of changes, and produces a clear human-readable report that can be posted either as a GitHub PR comment (Markdown) or as a JIRA comment (Wiki Markup).
    11 repo stars
  31. ▌
    Code Review · pekral bundle
    Use when senior PHP code review focused on architecture, business logic, and risk detection. Read-only.
    11 repo stars
  32. ▌
    Create Test · pekral
    Use when create or update tests to ensure full coverage for current changes
    11 repo stars
  33. ▌
    E2e Testing · pekral
    Use when writing or stabilizing Playwright end-to-end browser tests against a Laravel app — but only when the project already has Playwright; otherwise defer to manual testing or Pest/Dusk.
    11 repo stars
  34. ▌
    Create Issue · pekral
    Use when create a single issue from provided text without modifying its content
    11 repo stars
  35. ▌
    Git Workflow · pekral
    Use when choosing a Git branching strategy or handling merge vs rebase, conflicts, stashing, undoing mistakes, and release tagging — complementing the commit/PR conventions in the git rules.
    11 repo stars
  36. ▌
    Design System · pekral
    Use when generating, auditing, or reviewing the visual design system of a Laravel app — Tailwind tokens, Filament theming, Blade/Livewire component consistency, and visual-polish audits.
    11 repo stars
  37. ▌
    Frontend A11Y · pekral
    Use when building or reviewing accessible UI in a Laravel app — semantic Blade markup, accessible forms, keyboard navigation with Alpine, focus and live-region management for Livewire updates, contrast, and Filament accessibility.
    11 repo stars
  38. ▌
    Resolve Issue · pekral bundle
    Use when resolving an issue from any supported tracker (GitHub, JIRA, Bugsnag). Detects the source automatically from the provided link or ID, implements a safe fix or feature, validates with tests, and creates a pull request.
    11 repo stars
  39. ▌
    Skill Creator · pekral
    Use when creating a new Agent skill in this repository. Generates a SKILL.md that follows project conventions, passes skill-check validation, and updates the changelog and readme.
    11 repo stars
  40. ▌
    Vite Patterns · pekral
    Use when configuring or optimizing Vite (laravel-vite-plugin) asset bundling in a Laravel app — entrypoints, the @vite Blade directive, HMR, env vars, aliases, manifests, code splitting, and production builds.
    11 repo stars
  41. ▌
    Mysql Patterns · pekral
    Use when designing MySQL schema features or applying advanced MySQL patterns in Laravel — upserts, JSON columns, full-text search, partitioning, replication/read-write splitting, and deadlock handling — beyond the query tuning already in the SQL rules.
    11 repo stars
  42. ▌
    Redis Patterns · pekral
    Use when using Redis in a Laravel app — caching strategies, atomic/distributed locks, rate limiting, stampede protection, pub/sub, pipelines, and key/TTL design beyond raw query tuning.
    11 repo stars
  43. ▌
    Analyze Problem · pekral bundle
    Use when structured problem analysis for debugging, root cause identification, and breaking down complex issues before proposing solutions
    11 repo stars
  44. ▌
    Article Writing · pekral
    Use when writing articles, guides, blog posts, tutorials, newsletter issues, or other long-form content longer than a paragraph, especially when voice consistency, structure, and credibility matter. Produces polished prose in a distinctive voice derived from supplied examples or a default operator voice.
    11 repo stars
  45. ▌
    Composer Update · pekral bundle
    Use when analyze composer update results, detect conflicts, and summarize changelogs of updated dependencies
    11 repo stars
  46. ▌
    Docker Patterns · pekral
    Use when writing or reviewing Docker and docker-compose setups for a Laravel application — multi-stage PHP-FPM images, services (nginx, MySQL, Redis, queue worker, scheduler, Vite build), healthchecks, secrets, and image hardening.
    11 repo stars
  47. ▌
    Frontend Slides · pekral
    Use when building standalone HTML/CSS/JS presentation slide decks — self-contained single-file decks with viewport-fit layout, keyboard navigation, and browser Print-to-PDF export.
    11 repo stars
  48. ▌
    Merge Github Pr · pekral
    Use when safely merge GitHub pull requests that are ready
    11 repo stars
  49. ▌
    Security Review · pekral bundle
    Use when performing a focused security review for Laravel/PHP projects. Prioritize real exploitability, business logic flaws, and high-risk vulnerabilities.
    11 repo stars
  50. ▌
    Slack Messaging · pekral bundle
    Use when you need to send messages to a Slack channel or read recent messages from a channel via the Slack Web API
    11 repo stars
  51. ▌
    Test Like Human · pekral bundle
    Use when testing a pull request from a real user perspective. Follow PR testing instructions, simulate realistic scenarios, and produce a human-readable report.
    11 repo stars
  52. ▌
    Tester Cookbook · pekral
    Use when preparing a concise QA report for an internal tester from a JIRA task and its linked pull requests — focused on what the tester should report back to the dev team — and posting it as a JIRA comment.
    11 repo stars
  53. ▌
    Autonomous Loops · pekral
    Use when choosing how to run Claude Code autonomously on this project — from a single sequential pipeline to multi-agent DAG orchestration. A reference catalog of loop patterns anchored to this repo's real tooling (resolve-issue, autoresolve-oldest-github-issue, code-review-github, process-code-review, merge-github-pr, /loop), with composer build / composer skill-check as the quality gate between iterations.
    11 repo stars
  54. ▌
    Code Review Jira · pekral bundle
    Use when run code review for JIRA issues and publish results to GitHub PR and JIRA
    11 repo stars
  55. ▌
    Laravel Security · pekral bundle
    Use when building, configuring, or hardening security-sensitive Laravel features — authentication, authorization, Eloquent safety, CSRF/XSS, API security, file uploads, secrets, and production configuration. Provides condensed, copy-ready secure defaults for Laravel 11 / PHP 8.3.
    11 repo stars
  56. ▌
    Production Audit · pekral
    Use when asked whether a change or app is production-ready, what could break in production, or for a ship/block decision before a release — assess readiness from cheap local git, code, CI, and config evidence and return a scored verdict with specific fixes.
    11 repo stars
  57. ▌
    Class Refactoring · pekral
    Use when refactor PHP classes to improve structure, readability, and maintainability while preserving behavior
    11 repo stars
  58. ▌
    Frontend Patterns · pekral
    Use when building Livewire/Blade/Alpine UI in a Laravel app — component composition, state placement, performance, forms, and loading/empty/error states.
    11 repo stars
  59. ▌
    Laravel Telescope · pekral bundle
    Use when analyzing Laravel Telescope requests from URL and DB. Loads Telescope entries, matches the same request in database tables, and proposes practical optimizations.
    11 repo stars
  60. ▌
    Postgres Patterns · pekral
    Use when designing PostgreSQL schema features or applying advanced Postgres patterns in Laravel — GIN/BRIN/partial/covering indexes, jsonb, ON CONFLICT upserts, SKIP LOCKED queue workers, cursor pagination, RLS, and timestamptz/numeric typing — beyond the query tuning already in the SQL rules.
    11 repo stars
  61. ▌
    Refresh Claude Md · pekral
    Use when the project's CLAUDE.md is stale or missing and must be regenerated from the current codebase — re-detect tech stack, commands, conventions, and structure, then update CLAUDE.md while preserving every human-authored customization. Adapted from the ECC codebase-onboarding skill.
    11 repo stars
  62. ▌
    Code Review Github · pekral bundle
    Use when perform code review for GitHub pull requests and post findings as PR comments plus a non-technical summary to every linked issue
    11 repo stars
  63. ▌
    Penetration Tester · pekral
    Use when the user explicitly requests a penetration test (pentest, ethical hacking, active exploitation, red-team assessment) against an authorized in-scope target — and only then. Runs a methodology-driven offensive assessment that validates exploitability with safe proofs of concept and delivers a risk-rated remediation report. Does not run on a normal code-review, security-review, or resolve-issue pass.
    11 repo stars
  64. ▌
    Product Capability · pekral
    Use when a PRD or product intent is clear but the implementation constraints are not — turns a vague capability ask into an engineering-ready plan that exposes invariants, interfaces, and unresolved decisions before any code is written.
    11 repo stars
  65. ▌
    Rewrite Tests Pest · pekral
    Use when rewriting existing tests to Pest syntax. Preserve behavior, follow project testing conventions, reduce duplication where helpful, and verify rewritten tests are deterministic and passing.
    11 repo stars
  66. ▌
    Code Review Bugsnag · pekral bundle
    Use when run code review for a Bugsnag error and publish results to the linked GitHub PR and the Bugsnag error
    11 repo stars
  67. ▌
    Process Code Review · pekral
    Use when processing pull request code review feedback. Finds the latest PR for a task, resolves review comments, updates review status, and triggers the next review cycle.
    11 repo stars
  68. ▌
    Automation Audit Ops · pekral
    Use when you need an evidence-first, read-only inventory of every automation in this repo (GitHub Actions, Claude Code hooks/settings, MCP servers, composer scripts, the bundled CLI installer, the skills catalog, scheduler/cron) before changing any of them, classifying each as live, broken, or redundant and recommending keep/merge/cut/fix.
    11 repo stars
  69. ▌
    Mysql Problem Solver · pekral bundle
    Use when analyze real MySQL query and schema problems using code inspection, schema review, and EXPLAIN when available
    11 repo stars
  70. ▌
    Pr Staged Merge Plan · pekral
    Use when a large pull request should be merged and deployed in safe parts instead of all at once. Analyzes every commit in the PR, groups them into atomic logical units that each ship independently without downtime, orders the units by dependency and rollback risk, proposes squashes for a clean human-readable history, and proposes corrected subjects for vague or inaccurate commit messages. Read-only — it proposes the plan and never rewrites history, pushes, or merges.
    11 repo stars
  71. ▌
    Prepare Issue Context · pekral
    Use when preparing data and context before /resolve-issue, TDD, or CR runs. Loads the assignment, extracts every concrete user scenario from the task description and acceptance criteria, maps each scenario to the codebase, seeds the development database with the records needed to reproduce the bug or feature end-to-end, and reports any gap that would force the implementing agent to hallucinate.
    11 repo stars
  72. ▌
    Record Project Memory · pekral
    Use when a task has converged (end of resolve-issue, process-code-review, or the final orchestrator report) and a durable, reusable lesson was learned. Distils only the lessons that clear a strict promotion bar and appends them — after a dedup/supersede/prune curation pass — to the per-project compound memory file, never recording trivia, secrets, or PII.
    11 repo stars
  73. ▌
    Cleanup Local Branches · pekral
    Use when cleaning up local Git branches after origin pruning. Deletes local branches whose upstream was deleted on origin (marked gone) and local branches with no origin counterpart that have been inactive for more than six months, while always protecting the current branch and the default branches. Previews every deletion before running it.
    11 repo stars
  74. ▌
    Security Bounty Hunter · pekral
    Use when hunting for exploitable, remotely reachable vulnerabilities in a PHP/Laravel codebase for responsible disclosure or a bounty submission, not a general best-practices review. Biases toward user-controlled attack paths that pay and discards low-signal noise.
    11 repo stars
  75. ▌
    Create Issues From Text · pekral bundle
    Use when break down assignment into multiple structured issues
    11 repo stars
  76. ▌
    Test Driven Development · pekral
    Use when implementing a feature or bugfix with strict TDD. Enforce failing-test-first, minimal implementation, and safe refactoring.
    11 repo stars
  77. ▌
    Latency Critical Systems · pekral
    Use when working on latency-sensitive Laravel paths — realtime dashboards, streaming, queues, caches, or execution gateways — where p95 latency and data freshness matter.
    11 repo stars
  78. ▌
    Security Threat Analysis · pekral
    Use when analyzing a specific security threat from a referenced source (CVE, GHSA, security advisory, blog post, or write-up). Produces a human-readable remediation report with step-by-step instructions an AI agent can follow to eliminate the threat in the current project.
    11 repo stars
  79. ▌
    Frontend Design Direction · pekral
    Use when the work is not just making UI function but making it feel purposeful and polished — choosing a deliberate design direction for a Laravel/Blade/Livewire/Filament interface.
    11 repo stars
  80. ▌
    Smartest Project Addition · pekral
    Use when you want exactly one high-impact, concrete proposal for the next project addition.
    11 repo stars
  81. ▌
    Create Missing Tests In Pr · pekral
    Reads your pull request code review, verifies that all recommended test coverage is implemented in the codebase, and adds missing tests using the create-test skill. Use when a PR review already exists and missing tests must be completed with 100% coverage for current changes.
    11 repo stars
  82. ▌
    Assignment Compliance Check · pekral
    Use when checking that the pull request implementation actually fulfills the business requirements stated in the linked issue or task. Returns a plain-language markdown block that is the Functional review half of the two-part CR output (`@rules/code-review/general.mdc` Two-part CR output — Technical & Functional review): a full checklist of every extracted acceptance criterion with its status (Met / Not met / Partial / Divergent) and an explicit Goal met: Yes/No verdict, rendered on every run that has a linked tracker — including the fully affirmative report when every requirement is satisfied. No local file is created and the block is not embedded in the GitHub PR comment.
    11 repo stars
  83. ▌
    Benchmark Optimization Loop · pekral
    Use when a goal is vague speed ("make it faster", "reduce p95", "cut query time") and you need a bounded, measured loop that promotes only verified, correctness-preserving wins instead of guessed micro-tweaks.
    11 repo stars
  84. ▌
    Laravel Authorization Review · pekral bundle
    Use when reviewing authorization / access control in a Laravel project — find IDOR / broken object-level authorization (BOLA), audit which routes are unprotected, check policy / gate coverage, or sanity-check a new endpoint in a PR. Walks the authorization chain of every HTTP route (middleware → authorize/policy/gate → query scoping → API Resource output), anchors every finding to real `php artisan route:list --json` output plus a cited `file:line`, classifies by confidence, and produces a per-route coverage map. Read-only / advise-only — never edits code.
    11 repo stars
  85. ▌
    Codebase Simplification Audit · pekral
    Use when the user asks for an audit of the codebase or decides to refactor a part of it, and wants the cleanest achievable answer rather than a quick opinion. Runs a coordinator-driven, read-only sweep for materially useful simplifications in data structures, state representation, control flow, algorithms, and ownership — every subsystem inventoried, each finding independently verified, the audit itself audited. Proposes only; never edits, tests, commits, or pushes.
    11 repo stars
  86. ▌
    Refactor Entry Point To Action · pekral
    Use when refactoring controller, job, command, listener, or Livewire entry-point logic into a dedicated Action class while preserving behavior and response contracts.
    11 repo stars
  87. ▌
    Autoresolve Oldest Github Issue · pekral
    Use when autonomously resolving the oldest open GitHub issue end-to-end. Picks the oldest open issue (optionally filtered by label, default `Resolve_by_AI`), delegates resolution to `resolve-issue`, then runs `code-review-github`, `process-code-review`, and `merge-github-pr` on the resulting pull request. Stops and reports any blocker (merge conflict, failing CI, unresolved Critical/Moderate findings) instead of force-merging.
    11 repo stars
  88. ▌
    Understand Propose Implement Verify · pekral
    Use when following a strict problem-solving loop: understand, propose, implement, verify.
    11 repo stars