@ifi/oh-pi-prompts 0.2.1

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2025 Ifiok Jr.
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/package.json

@@ -0,0 +1,18 @@
+{
+  "name": "@ifi/oh-pi-prompts",
+  "version": "0.2.1",
+  "description": "Prompt templates for pi: review, fix, explain, refactor, test, commit, and more.",
+  "keywords": [
+    "pi-package"
+  ],
+  "pi": {
+    "prompts": [
+      "./prompts"
+    ]
+  },
+  "files": [
+    "prompts",
+    "README.md"
+  ],
+  "license": "MIT"
+}

package/prompts/commit.md

@@ -0,0 +1,21 @@
+---
+description: Generate a Conventional Commit message for staged changes
+---
+
+Generate a commit message for the current staged changes (`git diff --cached`).
+
+Follow Conventional Commits format:
+
+```
+type(scope): description
+
+[optional body]
+```
+
+Types: feat, fix, refactor, docs, test, chore, perf, ci, style, build
+
+- Keep the subject line under 72 characters
+- Use imperative mood ("add" not "added")
+- Body explains WHY, not WHAT (the diff shows what)
+
+$@

package/prompts/document.md

@@ -0,0 +1,15 @@
+---
+description: Generate or update documentation
+---
+
+Generate documentation for the following code. Include:
+
+1. **Overview** — What it does and why it exists
+2. **API** — Functions/methods with parameters, return types, examples
+3. **Usage** — How to use it with code examples
+4. **Configuration** — Available options and defaults
+5. **Error handling** — What errors can occur and how to handle them
+
+Match the project's existing documentation style. Use JSDoc/docstrings as appropriate.
+
+$@

package/prompts/explain.md

@@ -0,0 +1,14 @@
+---
+description: Explain code or concept clearly, from simple to detailed
+---
+
+Explain the following code or concept. Structure your explanation as:
+
+1. **One-liner** — What it does in one sentence
+2. **How it works** — Step-by-step walkthrough
+3. **Why** — Design decisions and trade-offs
+4. **Edge cases** — What could go wrong
+
+Adjust depth to the complexity. Use analogies when helpful.
+
+$@

package/prompts/fix.md

@@ -0,0 +1,12 @@
+---
+description: Fix the current error or bug with minimal changes
+---
+
+Fix the error/bug described below. Follow these principles:
+
+1. **Minimal change** — Only modify what's necessary to fix the issue
+2. **Root cause** — Fix the underlying cause, not just the symptom
+3. **No regressions** — Ensure existing behavior is preserved
+4. **Explain** — Briefly explain what caused the bug and why your fix works
+
+$@

package/prompts/optimize.md

@@ -0,0 +1,15 @@
+---
+description: Optimize code for performance
+---
+
+Optimize the following code for performance. Approach:
+
+1. **Measure first** — Identify the actual bottleneck
+2. **Algorithm** — Can we use a better data structure or algorithm?
+3. **I/O** — Reduce network calls, disk reads, unnecessary allocations
+4. **Caching** — What can be memoized or cached?
+5. **Concurrency** — Can work be parallelized?
+
+Show before/after with expected improvement. Don't sacrifice readability for micro-optimizations.
+
+$@

package/prompts/pr.md

@@ -0,0 +1,32 @@
+---
+description: Generate a pull request description
+---
+
+Generate a PR description based on the changes in this branch (`git log --oneline main..HEAD` and
+`git diff main`).
+
+Structure:
+
+## What
+
+Brief description of the change.
+
+## Why
+
+Motivation and context.
+
+## How
+
+Implementation approach and key decisions.
+
+## Testing
+
+How this was tested.
+
+## Checklist
+
+- [ ] Tests added/updated
+- [ ] Documentation updated
+- [ ] No breaking changes (or documented)
+
+$@

package/prompts/refactor.md

@@ -0,0 +1,15 @@
+---
+description: Refactor code while preserving behavior
+---
+
+Refactor the following code. Goals:
+
+1. **Preserve behavior** — No functional changes
+2. **Reduce complexity** — Simplify logic, extract functions if needed
+3. **Improve naming** — Clear, descriptive names
+4. **Remove duplication** — DRY without over-abstracting
+5. **Follow conventions** — Match the project's existing style
+
+Show the refactored code with a brief explanation of each change.
+
+$@

package/prompts/review.md

@@ -0,0 +1,20 @@
+---
+description: Review code for bugs, security issues, and improvements
+---
+
+Review the code I'm about to share (or the current file). Focus on:
+
+1. **Bugs & Logic Errors** — Off-by-one, null/undefined, race conditions
+2. **Security** — Injection, auth bypass, data exposure, hardcoded secrets
+3. **Error Handling** — Missing try/catch, unhandled promises, silent failures
+4. **Performance** — N+1 queries, unnecessary re-renders, memory leaks
+5. **Readability** — Naming, complexity, dead code
+
+For each issue found, provide:
+
+- Severity (🔴 Critical / 🟡 Warning / 🔵 Info)
+- Location (file:line)
+- Problem description
+- Suggested fix
+
+$@

package/prompts/security.md

@@ -0,0 +1,16 @@
+---
+description: Security audit following OWASP guidelines
+---
+
+Perform a security audit on the following code. Check for:
+
+1. **Injection** — SQL, XSS, command injection, path traversal
+2. **Authentication** — Weak auth, missing checks, session issues
+3. **Authorization** — Privilege escalation, IDOR, missing access control
+4. **Data Exposure** — Sensitive data in logs/responses, hardcoded secrets
+5. **Configuration** — Debug mode, default credentials, CORS misconfiguration
+6. **Dependencies** — Known vulnerable packages
+
+Rate each finding: 🔴 Critical / 🟠 High / 🟡 Medium / 🔵 Low Provide remediation for each.
+
+$@

package/prompts/test.md

@@ -0,0 +1,14 @@
+---
+description: Generate tests for the specified code
+---
+
+Write tests for the following code. Requirements:
+
+1. **Detect framework** — Use the project's existing test framework (Jest, Vitest, pytest, Go test,
+   etc.)
+2. **Cover** — Happy path, edge cases, error cases
+3. **Naming** — Descriptive test names that explain the scenario
+4. **Isolation** — Mock external dependencies
+5. **Assertions** — Specific assertions, not just "no error"
+
+$@