Resolve Issue
Role: Resolve GitHub issues end-to-end by running the auto-fix-bug workflow, then refactoring, reviewing, testing, and submitting via branch, commit, and PR.
Constraint: If the issue is closed or not ready for processing, do nothing.
1. Run Auto-Fix-Bug
Do:
- For each given issue URL, run the workflow from
.cursor/skills/auto-fix-bug/SKILL.md.
- If the problem is closed or not ready for processing, do nothing and stop.
- After resolve issues do
.cursor/skills/security-review/SKILL.md and for sql do .cursor/skills/database-optimizer/SKILL.md if needed.
2. Refactor
Do:
- After writing the code, refactor according to
.cursor/skills/class-refactoring/SKILL.md for all new PHP classes.
- Fix DRY, apply SOLID principles where appropriate, and enforce SRP.
3. Run Fixers
Do:
- Analyze
composer.json and run the most suitable fix script(s) (e.g. fix, pint-fix, phpcs-fix), if available.
4. Code Review
Do:
- Perform the code review defined in
.cursor/skills/code-review/SKILL.md.
- If any critical issues are found, ask the user and let them choose what to fix.
- If they choose something, modify the code and iterate again from step 2.
5. Test and Examples
Do:
- Test the functionality according to the assignment.
- If there are example files, analyze them and update them for the current changes or create new ones.
- If none exist, skip this point.
6. Submit
Do:
- If the code is ready for submission: create a new branch according to conventions, create a commit according to conventions, push the branch to the repository.
- After a successful push, switch to the main branch and send the user a link to the PR.
Converted and distributed by TomeVault — claim your Tome and manage your conversions.
1---2name: pekral-php-skeleton-resolve-issue3description: Resolve Issue4---56# Resolve Issue78**Role:** Resolve GitHub issues end-to-end by running the auto-fix-bug workflow, then refactoring, reviewing, testing, and submitting via branch, commit, and PR.910**Constraint:** If the issue is closed or not ready for processing, do nothing.1112---1314## 1. Run Auto-Fix-Bug1516**Do:**17- For each given issue URL, run the workflow from `.cursor/skills/auto-fix-bug/SKILL.md`.18- If the problem is closed or not ready for processing, do nothing and stop.19- After resolve issues do `.cursor/skills/security-review/SKILL.md` and for sql do `.cursor/skills/database-optimizer/SKILL.md` if needed.2021---2223## 2. Refactor2425**Do:**26- After writing the code, refactor according to `.cursor/skills/class-refactoring/SKILL.md` for all new PHP classes.27- Fix DRY, apply SOLID principles where appropriate, and enforce SRP.2829---3031## 3. Run Fixers3233**Do:**34- Analyze `composer.json` and run the most suitable fix script(s) (e.g. fix, pint-fix, phpcs-fix), if available.3536---3738## 4. Code Review3940**Do:**41- Perform the code review defined in `.cursor/skills/code-review/SKILL.md`.42- If any critical issues are found, ask the user and let them choose what to fix.43- If they choose something, modify the code and iterate again from step 2.4445---4647## 5. Test and Examples4849**Do:**50- Test the functionality according to the assignment.51- If there are example files, analyze them and update them for the current changes or create new ones.52- If none exist, skip this point.5354---5556## 6. Submit5758**Do:**59- If the code is ready for submission: create a new branch according to conventions, create a commit according to conventions, push the branch to the repository.60- After a successful push, switch to the main branch and send the user a link to the PR.6162---63> Converted and distributed by [TomeVault](https://tomevault.io/claim/pekral) — claim your Tome and manage your conversions.64<!-- tomevault:4.0:skill_md:2026-04-15 -->
tomevault-io