@myszon01/agentic-bundle-pi 0.0.0-stage → 0.1.0

package/AGENTS.md

@@ -0,0 +1,19 @@
+# Working agreements
+
+These instructions are shared by every coding agent this harness is installed into.
+
+## How to work
+
+- Read the relevant code before changing it; match the surrounding style, naming and comment density.
+- Prefer small, focused changes. Do not refactor unrelated code in the same change.
+- Run the project's own checks (tests, linter, type checker) before declaring work done, and report failures honestly.
+- Ask before destructive or hard-to-reverse actions (deleting data, force-pushing, rewriting history).
+
+## Commits
+
+- Use Conventional Commits (`type(scope): summary`). The `conventional-commits` skill has the details.
+- One logical change per commit; explain *why* in the body when it is not obvious.
+
+## Reviews
+
+- When asked to review, use the `code-review` skill and lead with correctness issues before style.

package/README.md

@@ -1,3 +1,25 @@
-# Temporary Holding Version
+# @myszon01/agentic-bundle-pi
 
-This version is a temporary placeholder for this package. An operational version to replace this has been submitted for review and is awaiting a staged release.
+pi package of agentic-bundle: A portable agentic harness: shared instructions, skills, commands, subagents and MCP servers.
+
+Generated with agentic-bundle from `agentic-bundle@0.1.0` for **pi**.
+
+## Install
+
+This package is a pi package (skills and prompt templates):
+
+```bash
+pi install npm:@myszon01/agentic-bundle-pi
+```
+
+pi packages cannot carry `AGENTS.md`. To install the shared instructions too:
+
+```bash
+npx -y @myszon01/agentic-bundle install pi --scope user
+```
+
+## Contents
+
+- `AGENTS.md`
+- `prompts`
+- `skills`

package/package.json

@@ -1,6 +1,32 @@
 {
   "name": "@myszon01/agentic-bundle-pi",
-  "version": "0.0.0-stage",
-  "stub": true,
-  "description": "Temporary package placeholder for staged publishing"
-}
+  "version": "0.1.0",
+  "description": "pi package of agentic-bundle: A portable agentic harness: shared instructions, skills, commands, subagents and MCP servers.",
+  "keywords": [
+    "pi-package",
+    "harness",
+    "skills",
+    "workflow",
+    "agentic-bundle",
+    "pi"
+  ],
+  "license": "MIT",
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/myszon01/agentic-bundle.git"
+  },
+  "pi": {
+    "skills": [
+      "./skills"
+    ],
+    "prompts": [
+      "./prompts"
+    ]
+  },
+  "author": {
+    "name": "myszon01"
+  },
+  "publishConfig": {
+    "access": "public"
+  }
+}

package/prompts/commit.md

@@ -0,0 +1,8 @@
+---
+description: Stage the current work and write a Conventional Commits message
+argument-hint: "[extra context]"
+---
+
+Look at `git status` and `git diff`, stage the changes that belong together, and commit them using the conventional-commits skill.
+
+Additional context from the user: $ARGUMENTS

package/prompts/review.md

@@ -0,0 +1,8 @@
+---
+description: Review the current changes (or the given target) for bugs and risks
+argument-hint: "[path, branch or PR]"
+---
+
+Use the code-review skill to review $ARGUMENTS.
+
+If no target was given, review the uncommitted changes plus any commits on the current branch that are not on the default branch.

package/skills/code-review/SKILL.md

@@ -0,0 +1,17 @@
+---
+name: code-review
+description: Review a diff or set of files for correctness, security and maintainability issues. Use when asked to review code, a pull request, or the current changes.
+---
+
+# Code review
+
+1. Collect the change. If nothing specific was given, run `scripts/changed-files.sh` to list files changed against the default branch, then read the diff.
+2. Review in this order, and stop to report anything severe:
+   1. **Correctness** — logic errors, unhandled edge cases, broken error handling, race conditions.
+   2. **Security** — injection, unsafe deserialization, secrets in code, missing authorization checks.
+   3. **Tests** — is the new behaviour covered? Do existing tests still make sense?
+   4. **Maintainability** — naming, duplication, dead code, unclear abstractions.
+3. For each finding give: file and line, what is wrong, a concrete failure scenario, and a suggested fix.
+4. Finish with a one-line verdict: *ship it*, *ship with nits*, or *needs changes*.
+
+Do not report style nits that a formatter or linter would catch.

package/skills/code-review/scripts/changed-files.sh

@@ -0,0 +1,5 @@
+#!/usr/bin/env sh
+# List files changed on the current branch relative to the default branch.
+set -eu
+base=$(git symbolic-ref --quiet --short refs/remotes/origin/HEAD 2>/dev/null || echo origin/main)
+git diff --name-only "$(git merge-base HEAD "$base" 2>/dev/null || echo HEAD)"

package/skills/conventional-commits/SKILL.md

@@ -0,0 +1,36 @@
+---
+name: conventional-commits
+description: Write commit messages that follow the Conventional Commits spec. Use when committing changes, drafting a commit message, or squashing a branch.
+---
+
+# Conventional Commits
+
+Format every commit message as:
+
+```
+<type>(<optional scope>): <imperative summary, max 72 chars>
+
+<optional body: what changed and why, wrapped at 72 chars>
+
+<optional footer: BREAKING CHANGE: ..., Refs: #123>
+```
+
+## Types
+
+| type       | use for                                             |
+|------------|-----------------------------------------------------|
+| `feat`     | a new user-facing capability                        |
+| `fix`      | a bug fix                                           |
+| `docs`     | documentation only                                  |
+| `refactor` | code change that neither fixes a bug nor adds a feature |
+| `perf`     | performance improvement                             |
+| `test`     | adding or fixing tests                              |
+| `build`    | build system or dependencies                        |
+| `ci`       | CI configuration                                    |
+| `chore`    | anything else that does not touch src or tests      |
+
+## Rules
+
+1. Summary in the imperative mood ("add", not "added"), no trailing period.
+2. Mark breaking changes with `!` after the type/scope **and** a `BREAKING CHANGE:` footer.
+3. Inspect the staged diff (`git diff --cached`) before writing the message; describe what it actually does.