pekral
29 verified skills53 total stars
test-like-human
Use when testing a pull request from a real user perspective. Follow PR testing instructions, simulate realistic scenarios, and produce a human-readable report.
testing2
autoresolve-oldest-github-issue
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.
development2
resolve-issue
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.
testing2
pr-summary
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).
development2
composer-update
Use when analyze composer update results, detect conflicts, and summarize changelogs of updated dependencies
testing2
create-issues-from-text
Use when break down assignment into multiple structured issues
tools2
assignment-compliance-check
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 listing only Critical functional gaps **only when at least one gap exists**; when the implementation satisfies every stated requirement the skill returns a skip status and the calling CR wrapper embeds nothing. The block (when present) carries actionable gaps only — never lists of satisfied requirements or open questions. No local file is created and the block is not embedded in the GitHub PR comment.
testing2
create-missing-tests-in-pr
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.
development2
create-test
Use when create or update tests to ensure full coverage for current changes
testing2
code-review
Use when senior PHP code review focused on architecture, business logic, and risk detection. Read-only.
development2
merge-github-pr
Use when safely merge GitHub pull requests that are ready
tools2
security-review
Use when performing a focused security review for Laravel/PHP projects. Prioritize real exploitability, business logic flaws, and high-risk vulnerabilities.
testing2
skill-creator
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.
testing2
refactor-entry-point-to-action
Use when refactoring controller, job, command, listener, or Livewire entry-point logic into a dedicated Action class while preserving behavior and response contracts.
development2
test-driven-development
Use when implementing a feature or bugfix with strict TDD. Enforce failing-test-first, minimal implementation, and safe refactoring.
development2
prepare-issue-context
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.
development2
analyze-problem
Use when structured problem analysis for debugging, root cause identification, and breaking down complex issues before proposing solutions
development2
mysql-problem-solver
Use when analyze real MySQL query and schema problems using code inspection, schema review, and EXPLAIN when available
development2
code-review-jira
Use when run code review for JIRA issues and publish results to GitHub PR and JIRA
development2
code-review-github
Use when perform code review for GitHub pull requests and post findings as PR comments plus a non-technical summary to every linked issue
development2
class-refactoring
Use when refactor PHP classes to improve structure, readability, and maintainability while preserving behavior
development2
tester-cookbook
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.
development2
process-code-review
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.
development2
security-threat-analysis
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.
testing2
laravel-telescope
Use when analyzing Laravel Telescope requests from URL and DB. Loads Telescope entries, matches the same request in database tables, and proposes practical optimizations.
data-ai1
understand-propose-implement-verify
Use when following a strict problem-solving loop: understand, propose, implement, verify.
testing1
rewrite-tests-pest
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.
testing1
create-issue
Use when create a single issue from provided text without modifying its content
content-media1
smartest-project-addition
Use when you want exactly one high-impact, concrete proposal for the next project addition.
testing1