npm - @mohammadhprp/system-prompt - Versions diffs - 0.12.4 → 0.12.6 - Mend

@mohammadhprp/system-prompt 0.12.4 → 0.12.6

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (43) hide show

package/framework/commands/pr.md DELETED Viewed

@@ -1,39 +0,0 @@
----
-description: Create a GitHub PR for the current branch
-agent: build
----
-PR $ARGUMENTS
-Create or update a pull request for the current branch using `gh` cli.
-## Process
-1. **Collect information**
-   - Get current branch name: `git branch --show-current`
-   - Read PR template from `.github/pull_request_template.md` of exsits
-2. **Format PR title**
-   - Take the branch name, replace all `-` with spaces, capitalize first character
-3. **Collect commits and build summary**
-   - List commits on the branch that are not on `dev`: `git log dev..HEAD --oneline`
-   - Read each commit message, convert to a bullet list summarizing user-facing changes
-   - Merge/squash related commits (e.g. multiple commits for the same change)
-   - Keep concise, one bullet per logical change
-4. **Fill template**
-   - Set Summary to the bullet list from step 3
-   - Keep the Checklist section as-is
-5. **Present plan and confirm** - Show:
-   - Source branch
-   - Target branch: `develop`
-   - Title
-   - Filled description
-   - Ask: "Shall I create this PR?"
-   - Push the changes if user says Yes
-6. **Create upon confirmation** - Use `gh` cli:
-   - `gh pr create --title "<title>" --body "<body>" --base <target>`
-   - Show the resulting URL.

package/framework/commands/release.md DELETED Viewed

@@ -1,34 +0,0 @@
----
-description: Create a release by tagging the current state, generating changelog, and bumping version
-agent: build
----
-Release $ARGUMENTS
-Create a release from the current branch state.
-## Process
-1. **Review recent commits** - Run `git fetch --tags`, `git describe --tags --abbrev=0` to find the latest tag. Run `git log <latest-tag>..HEAD --oneline --format="%s"` to collect all conventional commits since the last release. Read any existing `CHANGELOG.md`.
-2. **Categorize commits** - Group commits by conventional commit type:
-   - `feat!:` or `BREAKING CHANGE:` → breaking change
-   - `feat:` → minor feature
-   - `fix:` → patch fix
-   - `perf:`, `refactor:`, `test:` → patch (if no features)
-   - `chore:`, `docs:`, `ci:` → filtered from changelog
-3. **Determine next version** - Based on the [`commit.md`](./commit.md) semver convention:
-   - Breaking changes → increment major version (e.g., `1.2.3` → `2.0.0`)
-   - New features → increment minor version (e.g., `1.2.3` → `1.3.0`)
-   - Only fixes/refactors → increment patch version (e.g., `1.2.3` → `1.3.4`)
-   - If no previous tag exists, propose `0.1.0`
-4. **Present release plan** - Show: current version, new version, categorized changelog entries, and ask: "Shall I create this release (tag vX.Y.Z and update CHANGELOG.md)?"
-5. **Execute on confirmation**:
-   - Update `CHANGELOG.md`: create a new `## [vX.Y.Z]` section under `## Unreleased`, move categorized entries (excluding chore/docs/ci) into it, add the release date, keep the `## Unreleased` section empty for future work
-   - Run `git add CHANGELOG.md && git commit -m "chore: release vX.Y.Z"`
-   - Run `git tag -a vX.Y.Z -m "vX.Y.Z"`
-6. **Verify** - Run `git log --oneline -n 3` and `git tag --list --sort=-v:refname -n5` to confirm the release tag and commit are in place.

package/framework/commands/review.md DELETED Viewed

@@ -1,24 +0,0 @@
----
-description: Perform comprehensive code quality review
-agent: plan
----
-Review $ARGUMENTS
-Perform comprehensive code quality review.
-## Process
-1. **Review conversation and diff** - Read conversation history, run `git diff` for staged/unstaged changes, identify the problem being solved and the behavior being modified. Read related standards: [`references/standards/naming.md`](../references/standards/naming.md), [`references/standards/testing.md`](../references/standards/testing.md), [`references/standards/security.md`](../references/standards/security.md), [`references/standards/performance.md`](../references/standards/performance.md).
-2. **Check correctness** - Edge cases, concurrency, error handling, state transitions, backward compatibility. Read contracts and interfaces before implementation.
-3. **Check maintainability** - Naming reflects business meaning, structure matches project conventions, comments explain why not what.
-4. **Check testing** - Do tests prove the behavior change? Missing edge cases or failure paths? Tests should verify behavior, not mirror implementation.
-5. **Check performance** - N+1 queries, unbounded loops, unnecessary allocations, caching opportunities.
-6. **Check security** - Input validation, authentication enforcement, secrets exposure, least privilege.
-7. **Present findings** - Distinguish blockers from suggestions, explain reasoning for each, summarize overall risk and production readiness.