blogr

Analyzes Git changes, proposes CHANGELOG.md entries (user validation required), creates atomic Conventional Commits, places work on a type-named branch (feat, fix, docs…), and proposes a GitHub Pull Request. Use when the user asks to commit changes, update the changelog, prepare a branch/PR, or finalize work with atomic commits.

Orchestrates the full cycle from a need or bug to pull request: GitHub issue creation, code analysis, development generation, then calls the git-changelog workflow for atomic commits and PR. Use when the user reports a bug, requests a feature, or describes a need without specifying the implementation steps.

Automate Blogr package releases: version bumping, CHANGELOG updates, tagging, and publishing to GitHub.

Audits all quality axes of the Blogr package (tests, static analysis, code style, JS/CSS linting, CI, coverage, pre-commit hooks) and proposes one improvement at a time, validated by the human before execution. Use when starting a new development phase, after a sprint, or when the user asks to review or improve the project's quality infrastructure.

Apply a fix from a feature branch already merged to main when main has advanced. Use `git cherry-pick` to port a fix commit without rebasing the entire branch.

Detects and resolves Git merge conflicts typical of a Laravel package project with parallel feature branches. Covers conflicts on service providers, Filament Schema components, Translation-First models, and config files.

Runs a static OWASP Top 10 security audit on Blogr (Laravel 12.x, FilamentPHP v4, SQLite, blocks-based content, Translation-First). Covers only the five most critical categories: A01 access control, A02 cryptographic failures, A03 injection, A05 misconfiguration, A07 authentication failures. Use when the user asks for a security audit, OWASP review, vulnerability scan of package code, or to refresh SECURITY-AUDIT.md.

Scans Composer and npm dependencies, applies security filters (minimum age 72h, CVE detection), classifies updates by type (patch/minor/major), and presents a human-validated plan before execution and testing. Use when the user asks to update dependencies, review outdated packages, check for security advisories, or run composer audit / npm audit.

Isolate code from parallel sprints mixed in the same working tree into clean Git branches. Backup the working tree, then cherry-pick files sprint by sprint into dedicated branches from main.