pekral
- 88 skills
- 0 followers
- 11 repo stars
- 2 days ago last updated
- ▌ Auto Interactive Testing · pekral bundleUse 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.
- ▌ Machine Payments Protocol · pekral bundleUse 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.
- ▌ Create Missing Tests In Pr 2 · pekralUse 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.
- ▌ Git History Exposure Audit · pekral bundleUse 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.
- ▌ Laravel Architecture Guard · pekralUse 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.
- ▌ Test Assignment · pekral bundleUse 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.
- ▌ Composer Update Pr · pekral bundleUse 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.
- ▌ Web Article Writer · pekralUse 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.
- ▌ Github Issue Triage · pekral bundleUse 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.
- ▌ Interactive Testing · pekral bundleUse 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.
- ▌ Merge Github Pr Fast · pekral bundleUse 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.
- ▌ Simplification Audit · pekral bundleUse 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.
- ▌ Analyze Support Issue · pekral bundleUse 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.
- ▌ Blast Radius Analysis · pekralUse 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.
- ▌ Deliver Page Redesign · pekralUse 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.
- ▌ Github Release Roadmap · pekral bundleUse 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.
- ▌ Verify Merge Readiness · pekral bundleUse 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.
- ▌ Do It · pekral bundleUse 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.
- ▌ Test Audit · pekral bundleUse 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.
- ▌ Agent Voice · pekral bundleUse 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.
- ▌ Create Test 2 · pekralUse 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.
- ▌ Git Workflow 2 · pekralUse 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.
- ▌ Page Redesign · pekral bundleUse 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.
- ▌ Diagram Design · pekral bundleUse 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.
- ▌ Security Audit · pekral bundleUse 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.
- ▌ SEO · pekralUse 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.
- ▌ Benchmark · pekralUse 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.
- ▌ Blueprint · pekralUse 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.
- ▌ API Review · pekral bundleUse 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.
- ▌ Pr Summary · pekral bundleUse 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).
- ▌ Code Review · pekral bundleUse when senior PHP code review focused on architecture, business logic, and risk detection. Read-only.
- ▌
- ▌ E2e Testing · pekralUse 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.
- ▌ Create Issue · pekralUse when create a single issue from provided text without modifying its content
- ▌ Git Workflow · pekralUse 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.
- ▌ Design System · pekralUse 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.
- ▌ Frontend A11Y · pekralUse 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.
- ▌ Resolve Issue · pekral bundleUse 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.
- ▌ Skill Creator · pekralUse 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.
- ▌ Vite Patterns · pekralUse 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.
- ▌ Mysql Patterns · pekralUse 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.
- ▌ Redis Patterns · pekralUse 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.
- ▌ Analyze Problem · pekral bundleUse when structured problem analysis for debugging, root cause identification, and breaking down complex issues before proposing solutions
- ▌ Article Writing · pekralUse 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.
- ▌ Composer Update · pekral bundleUse when analyze composer update results, detect conflicts, and summarize changelogs of updated dependencies
- ▌ Docker Patterns · pekralUse 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.
- ▌ Frontend Slides · pekralUse 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.
- ▌
- ▌ Security Review · pekral bundleUse when performing a focused security review for Laravel/PHP projects. Prioritize real exploitability, business logic flaws, and high-risk vulnerabilities.
- ▌ Slack Messaging · pekral bundleUse when you need to send messages to a Slack channel or read recent messages from a channel via the Slack Web API
- ▌ Test Like Human · pekral bundleUse when testing a pull request from a real user perspective. Follow PR testing instructions, simulate realistic scenarios, and produce a human-readable report.
- ▌ Tester Cookbook · pekralUse 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.
- ▌ Autonomous Loops · pekralUse 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.
- ▌ Code Review Jira · pekral bundleUse when run code review for JIRA issues and publish results to GitHub PR and JIRA
- ▌ Laravel Security · pekral bundleUse 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.
- ▌ Production Audit · pekralUse 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.
- ▌ Class Refactoring · pekralUse when refactor PHP classes to improve structure, readability, and maintainability while preserving behavior
- ▌ Frontend Patterns · pekralUse when building Livewire/Blade/Alpine UI in a Laravel app — component composition, state placement, performance, forms, and loading/empty/error states.
- ▌ Laravel Telescope · pekral bundleUse when analyzing Laravel Telescope requests from URL and DB. Loads Telescope entries, matches the same request in database tables, and proposes practical optimizations.
- ▌ Postgres Patterns · pekralUse 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.
- ▌ Refresh Claude Md · pekralUse 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.
- ▌ Code Review Github · pekral bundleUse when perform code review for GitHub pull requests and post findings as PR comments plus a non-technical summary to every linked issue
- ▌ Penetration Tester · pekralUse 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.
- ▌ Product Capability · pekralUse 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.
- ▌ Rewrite Tests Pest · pekralUse 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.
- ▌ Code Review Bugsnag · pekral bundleUse when run code review for a Bugsnag error and publish results to the linked GitHub PR and the Bugsnag error
- ▌ Process Code Review · pekralUse 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.
- ▌ Automation Audit Ops · pekralUse 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.
- ▌ Mysql Problem Solver · pekral bundleUse when analyze real MySQL query and schema problems using code inspection, schema review, and EXPLAIN when available
- ▌ Pr Staged Merge Plan · pekralUse 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.
- ▌ Prepare Issue Context · pekralUse 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.
- ▌ Record Project Memory · pekralUse 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.
- ▌ Cleanup Local Branches · pekralUse 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.
- ▌ Security Bounty Hunter · pekralUse 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.
- ▌ Create Issues From Text · pekral bundleUse when break down assignment into multiple structured issues
- ▌ Test Driven Development · pekralUse when implementing a feature or bugfix with strict TDD. Enforce failing-test-first, minimal implementation, and safe refactoring.
- ▌ Latency Critical Systems · pekralUse when working on latency-sensitive Laravel paths — realtime dashboards, streaming, queues, caches, or execution gateways — where p95 latency and data freshness matter.
- ▌ Security Threat Analysis · pekralUse 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.
- ▌ Frontend Design Direction · pekralUse 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.
- ▌ Smartest Project Addition · pekralUse when you want exactly one high-impact, concrete proposal for the next project addition.
- ▌ Create Missing Tests In Pr · pekralReads 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.
- ▌ Assignment Compliance Check · pekralUse 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.
- ▌ Benchmark Optimization Loop · pekralUse 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.
- ▌ Laravel Authorization Review · pekral bundleUse 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.
- ▌ Codebase Simplification Audit · pekralUse 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.
- ▌ Refactor Entry Point To Action · pekralUse when refactoring controller, job, command, listener, or Livewire entry-point logic into a dedicated Action class while preserving behavior and response contracts.
- ▌ Autoresolve Oldest Github Issue · pekralUse 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.
- ▌ Understand Propose Implement Verify · pekralUse when following a strict problem-solving loop: understand, propose, implement, verify.