@pigcloud/skills 1.0.10 → 1.1.2

package/skills/04-validation/security-review/references/README.md

@@ -0,0 +1,17 @@
+# security-review References
+
+This directory is local to the skill and is the only reference entry point for this skill.
+
+## Contents
+
+- `../skill-spec.json`: design source for regenerating this skill
+- `prompt-template.md`: reusable prompt wording for this skill
+- `cases.md`: human-readable replay case for this skill
+- `../assets/golden-prompt-suite.current.js`: machine-readable local case fixture
+
+## Guidance
+
+- Keep skill-specific explanation here instead of pushing it into a stage-level shared library.
+- Keep shared hard constraints in `../../../rules/index.md`.
+- Keep canonical names unchanged.
+- Skill summary: Review changes for authorization, data exposure, secrets, and abuse risk.

package/skills/04-validation/security-review/references/cases.md

@@ -0,0 +1,26 @@
+# security-review
+
+## Replay Case
+
+- Case: `security-risk-check`
+- First skill: `security-review`
+
+### Prompt
+
+```text
+Check whether this change introduces auth, injection, or data exposure risks.
+```
+
+### Expected Output
+
+- security findings
+- risk level
+- mitigation
+
+### Stop Rule
+
+- Do not rewrite code.
+
+### Handoff
+
+- regression-check

package/skills/04-validation/security-review/references/prompt-template.md

@@ -0,0 +1,18 @@
+# security-review
+
+## Prompt Template
+
+```text
+You are handling the security-review skill.
+Goal: Review changes for authorization, data exposure, secrets, and abuse risk
+Inputs: the request, supporting evidence, constraints, and existing repository facts.
+Output contract: security findings, risk level, mitigation.
+Stop rule: Do not rewrite code.
+Handoff: regression-check.
+Keep the response scoped to this stage and do not absorb the work of the next stage.
+```
+
+## Notes
+
+- Keep the template aligned with the local replay case and local assets.
+- Read `cases.md` for the matching replay example.

package/skills/04-validation/security-review/skill-spec.json

@@ -0,0 +1,25 @@
+{
+  "group": "04-validation",
+  "name": "security-review",
+  "description": "Review changes for authorization, data exposure, secrets, and abuse risk.",
+  "title": "Security Review",
+  "purpose": "Find security weaknesses and recommend the smallest safe mitigation.",
+  "whenToUse": [
+    "The change touches auth, secrets, data access, user input, or trust boundaries.",
+    "You need a security-specific review.",
+    "The risk is about exposure, privilege, or abuse rather than correctness alone."
+  ],
+  "how": [
+    "Check auth, data exposure, input handling, and trust boundaries before merge.",
+    "Trace how untrusted input reaches sensitive operations or secrets.",
+    "State the attack path, impacted asset, and minimum fix needed to close it.",
+    "Keep findings focused on concrete exploitability or exposure."
+  ],
+  "whenToAvoid": [
+    "You still need design or implementation work.",
+    "The task is about a different validation subtype.",
+    "You need to rewrite code instead of reviewing it."
+  ],
+  "caseId": "security-risk-check",
+  "source": "bootstrap-from-skill-md"
+}

package/skills/04-validation/unit-test/SKILL.md

@@ -0,0 +1,29 @@
+---
+name: unit-test
+description: Add or update focused tests that prove local behavior and guard regressions.
+---
+
+# Unit Test
+
+## Purpose
+
+Create small, deterministic tests that verify a change at the narrowest useful scope.
+
+## When to Use
+
+- The implementation needs automated proof.
+- You need fast feedback on a local behavior.
+- A regression should fail fast without running the whole stack.
+
+## How
+
+- Derive focused test cases from the behavior and cover the important edges first.
+- Prefer one behavior per test so failures point to one cause.
+- Include the boundary, error, and edge cases that protect the fix.
+- Keep fixtures and mocks as small as possible.
+
+## When to Avoid
+
+- You still need design or implementation work.
+- The task is about a different validation subtype.
+- You need to rewrite code instead of reviewing it.

package/skills/04-validation/unit-test/assets/golden-prompt-suite.current.js

@@ -0,0 +1,22 @@
+#!/usr/bin/env node
+
+module.exports = {
+  "name": "unit-test.golden-prompt-suite.current",
+  "skill": "unit-test",
+  "description": "Add or update focused tests that prove local behavior and guard regressions.",
+  "cases": [
+    {
+      "id": "unit-test-behavior-coverage",
+      "prompt": "This behavior needs tests. Design unit tests that cover the expected behavior.",
+      "expectedFirstSkill": "unit-test",
+      "expectedOutput": [
+        "test cases",
+        "assertions",
+        "edge cases"
+      ],
+      "expectedStop": "Do not modify production code.",
+      "expectedHandoff": "code-review"
+    }
+  ]
+};
+

package/skills/04-validation/unit-test/references/README.md

@@ -0,0 +1,17 @@
+# unit-test References
+
+This directory is local to the skill and is the only reference entry point for this skill.
+
+## Contents
+
+- `../skill-spec.json`: design source for regenerating this skill
+- `prompt-template.md`: reusable prompt wording for this skill
+- `cases.md`: human-readable replay case for this skill
+- `../assets/golden-prompt-suite.current.js`: machine-readable local case fixture
+
+## Guidance
+
+- Keep skill-specific explanation here instead of pushing it into a stage-level shared library.
+- Keep shared hard constraints in `../../../rules/index.md`.
+- Keep canonical names unchanged.
+- Skill summary: Add or update focused tests that prove local behavior and guard regressions.

package/skills/04-validation/unit-test/references/cases.md

@@ -0,0 +1,26 @@
+# unit-test
+
+## Replay Case
+
+- Case: `unit-test-behavior-coverage`
+- First skill: `unit-test`
+
+### Prompt
+
+```text
+This behavior needs tests. Design unit tests that cover the expected behavior.
+```
+
+### Expected Output
+
+- test cases
+- assertions
+- edge cases
+
+### Stop Rule
+
+- Do not modify production code.
+
+### Handoff
+
+- code-review

package/skills/04-validation/unit-test/references/prompt-template.md

@@ -0,0 +1,18 @@
+# unit-test
+
+## Prompt Template
+
+```text
+You are handling the unit-test skill.
+Goal: Add or update focused tests that prove local behavior and guard regressions
+Inputs: the request, supporting evidence, constraints, and existing repository facts.
+Output contract: test cases, assertions, edge cases.
+Stop rule: Do not modify production code.
+Handoff: code-review.
+Keep the response scoped to this stage and do not absorb the work of the next stage.
+```
+
+## Notes
+
+- Keep the template aligned with the local replay case and local assets.
+- Read `cases.md` for the matching replay example.

package/skills/04-validation/unit-test/skill-spec.json

@@ -0,0 +1,25 @@
+{
+  "group": "04-validation",
+  "name": "unit-test",
+  "description": "Add or update focused tests that prove local behavior and guard regressions.",
+  "title": "Unit Test",
+  "purpose": "Create small, deterministic tests that verify a change at the narrowest useful scope.",
+  "whenToUse": [
+    "The implementation needs automated proof.",
+    "You need fast feedback on a local behavior.",
+    "A regression should fail fast without running the whole stack."
+  ],
+  "how": [
+    "Derive focused test cases from the behavior and cover the important edges first.",
+    "Prefer one behavior per test so failures point to one cause.",
+    "Include the boundary, error, and edge cases that protect the fix.",
+    "Keep fixtures and mocks as small as possible."
+  ],
+  "whenToAvoid": [
+    "You still need design or implementation work.",
+    "The task is about a different validation subtype.",
+    "You need to rewrite code instead of reviewing it."
+  ],
+  "caseId": "unit-test-behavior-coverage",
+  "source": "bootstrap-from-skill-md"
+}

package/skills/05-delivery/change-log/SKILL.md

@@ -0,0 +1,29 @@
+---
+name: change-log
+description: Record what changed, why, and what evidence or follow-up matters.
+---
+
+# Change Log
+
+## Purpose
+
+Capture the important facts of a change for future review and handoff.
+
+## When to Use
+
+- You need a concise change summary.
+- The work should be traceable later.
+- Future readers need the why, not just the what.
+
+## How
+
+- Summarize what changed, why it changed, and what downstream readers need to know.
+- Record the impact, risk, and any validation evidence worth preserving.
+- Keep it short enough to scan but specific enough to reuse.
+- Add follow-up notes only when they affect future work.
+
+## When to Avoid
+
+- The delivery is not ready yet.
+- You need to change code rather than document release steps.
+- The request is only a short change summary.

package/skills/05-delivery/change-log/assets/golden-prompt-suite.current.js

@@ -0,0 +1,22 @@
+#!/usr/bin/env node
+
+module.exports = {
+  "name": "change-log.golden-prompt-suite.current",
+  "skill": "change-log",
+  "description": "Record what changed, why, and what evidence or follow-up matters.",
+  "cases": [
+    {
+      "id": "changelog-summary",
+      "prompt": "Summarize this change into a clear changelog entry.",
+      "expectedFirstSkill": "change-log",
+      "expectedOutput": [
+        "change summary",
+        "impact",
+        "notes"
+      ],
+      "expectedStop": "Do not rewrite implementation details.",
+      "expectedHandoff": "deployment-guide"
+    }
+  ]
+};
+

package/skills/05-delivery/change-log/references/README.md

@@ -0,0 +1,17 @@
+# change-log References
+
+This directory is local to the skill and is the only reference entry point for this skill.
+
+## Contents
+
+- `../skill-spec.json`: design source for regenerating this skill
+- `prompt-template.md`: reusable prompt wording for this skill
+- `cases.md`: human-readable replay case for this skill
+- `../assets/golden-prompt-suite.current.js`: machine-readable local case fixture
+
+## Guidance
+
+- Keep skill-specific explanation here instead of pushing it into a stage-level shared library.
+- Keep shared hard constraints in `../../../rules/index.md`.
+- Keep canonical names unchanged.
+- Skill summary: Record what changed, why, and what evidence or follow-up matters.

package/skills/05-delivery/change-log/references/cases.md

@@ -0,0 +1,26 @@
+# change-log
+
+## Replay Case
+
+- Case: `changelog-summary`
+- First skill: `change-log`
+
+### Prompt
+
+```text
+Summarize this change into a clear changelog entry.
+```
+
+### Expected Output
+
+- change summary
+- impact
+- notes
+
+### Stop Rule
+
+- Do not rewrite implementation details.
+
+### Handoff
+
+- deployment-guide

package/skills/05-delivery/change-log/references/prompt-template.md

@@ -0,0 +1,18 @@
+# change-log
+
+## Prompt Template
+
+```text
+You are handling the change-log skill.
+Goal: Record what changed, why, and what evidence or follow-up matters
+Inputs: the request, supporting evidence, constraints, and existing repository facts.
+Output contract: change summary, impact, notes.
+Stop rule: Do not rewrite implementation details.
+Handoff: deployment-guide.
+Keep the response scoped to this stage and do not absorb the work of the next stage.
+```
+
+## Notes
+
+- Keep the template aligned with the local replay case and local assets.
+- Read `cases.md` for the matching replay example.

package/skills/05-delivery/change-log/skill-spec.json

@@ -0,0 +1,25 @@
+{
+  "group": "05-delivery",
+  "name": "change-log",
+  "description": "Record what changed, why, and what evidence or follow-up matters.",
+  "title": "Change Log",
+  "purpose": "Capture the important facts of a change for future review and handoff.",
+  "whenToUse": [
+    "You need a concise change summary.",
+    "The work should be traceable later.",
+    "Future readers need the why, not just the what."
+  ],
+  "how": [
+    "Summarize what changed, why it changed, and what downstream readers need to know.",
+    "Record the impact, risk, and any validation evidence worth preserving.",
+    "Keep it short enough to scan but specific enough to reuse.",
+    "Add follow-up notes only when they affect future work."
+  ],
+  "whenToAvoid": [
+    "The delivery is not ready yet.",
+    "You need to change code rather than document release steps.",
+    "The request is only a short change summary."
+  ],
+  "caseId": "changelog-summary",
+  "source": "bootstrap-from-skill-md"
+}

package/skills/05-delivery/deployment-guide/SKILL.md

@@ -0,0 +1,29 @@
+---
+name: deployment-guide
+description: Document how to deploy, verify, or roll back a delivered change.
+---
+
+# Deployment Guide
+
+## Purpose
+
+Provide actionable deployment and rollback guidance for the current delivery.
+
+## When to Use
+
+- Someone needs to operate or hand off the release.
+- The deployment process needs a clear reference.
+- Startup, verification, troubleshooting, or rollback steps are required.
+
+## How
+
+- Capture startup, verify, troubleshoot, and recover steps for the delivered change.
+- Make the guide executable: prerequisites, commands, checks, and recovery steps.
+- Note anything that must be observed during rollout or immediately after it.
+- Keep the instructions tied to the current delivered artifact.
+
+## When to Avoid
+
+- The delivery is not ready yet.
+- You need to change code rather than document release steps.
+- The request is only a short change summary.

package/skills/05-delivery/deployment-guide/assets/golden-prompt-suite.current.js

@@ -0,0 +1,22 @@
+#!/usr/bin/env node
+
+module.exports = {
+  "name": "deployment-guide.golden-prompt-suite.current",
+  "skill": "deployment-guide",
+  "description": "Document how to deploy, verify, or roll back a delivered change.",
+  "cases": [
+    {
+      "id": "deployment-runbook",
+      "prompt": "Write the deployment and startup guide for this capability.",
+      "expectedFirstSkill": "deployment-guide",
+      "expectedOutput": [
+        "startup",
+        "verify",
+        "recover"
+      ],
+      "expectedStop": "Do not change product scope.",
+      "expectedHandoff": "codebase-learning"
+    }
+  ]
+};
+

package/skills/05-delivery/deployment-guide/references/README.md

@@ -0,0 +1,17 @@
+# deployment-guide References
+
+This directory is local to the skill and is the only reference entry point for this skill.
+
+## Contents
+
+- `../skill-spec.json`: design source for regenerating this skill
+- `prompt-template.md`: reusable prompt wording for this skill
+- `cases.md`: human-readable replay case for this skill
+- `../assets/golden-prompt-suite.current.js`: machine-readable local case fixture
+
+## Guidance
+
+- Keep skill-specific explanation here instead of pushing it into a stage-level shared library.
+- Keep shared hard constraints in `../../../rules/index.md`.
+- Keep canonical names unchanged.
+- Skill summary: Document how to deploy, verify, or roll back a delivered change.

package/skills/05-delivery/deployment-guide/references/cases.md

@@ -0,0 +1,26 @@
+# deployment-guide
+
+## Replay Case
+
+- Case: `deployment-runbook`
+- First skill: `deployment-guide`
+
+### Prompt
+
+```text
+Write the deployment and startup guide for this capability.
+```
+
+### Expected Output
+
+- startup
+- verify
+- recover
+
+### Stop Rule
+
+- Do not change product scope.
+
+### Handoff
+
+- codebase-learning

package/skills/05-delivery/deployment-guide/references/prompt-template.md

@@ -0,0 +1,18 @@
+# deployment-guide
+
+## Prompt Template
+
+```text
+You are handling the deployment-guide skill.
+Goal: Document how to deploy, verify, or roll back a delivered change
+Inputs: the request, supporting evidence, constraints, and existing repository facts.
+Output contract: startup, verify, recover.
+Stop rule: Do not change product scope.
+Handoff: codebase-learning.
+Keep the response scoped to this stage and do not absorb the work of the next stage.
+```
+
+## Notes
+
+- Keep the template aligned with the local replay case and local assets.
+- Read `cases.md` for the matching replay example.

package/skills/05-delivery/deployment-guide/skill-spec.json

@@ -0,0 +1,25 @@
+{
+  "group": "05-delivery",
+  "name": "deployment-guide",
+  "description": "Document how to deploy, verify, or roll back a delivered change.",
+  "title": "Deployment Guide",
+  "purpose": "Provide actionable deployment and rollback guidance for the current delivery.",
+  "whenToUse": [
+    "Someone needs to operate or hand off the release.",
+    "The deployment process needs a clear reference.",
+    "Startup, verification, troubleshooting, or rollback steps are required."
+  ],
+  "how": [
+    "Capture startup, verify, troubleshoot, and recover steps for the delivered change.",
+    "Make the guide executable: prerequisites, commands, checks, and recovery steps.",
+    "Note anything that must be observed during rollout or immediately after it.",
+    "Keep the instructions tied to the current delivered artifact."
+  ],
+  "whenToAvoid": [
+    "The delivery is not ready yet.",
+    "You need to change code rather than document release steps.",
+    "The request is only a short change summary."
+  ],
+  "caseId": "deployment-runbook",
+  "source": "bootstrap-from-skill-md"
+}

package/skills/05-delivery/release-check/SKILL.md

@@ -0,0 +1,29 @@
+---
+name: release-check
+description: Confirm a change is ready for release with the required gates and evidence.
+---
+
+# Release Check
+
+## Purpose
+
+Verify the change is release-ready from scope, risk, and evidence perspectives.
+
+## When to Use
+
+- A change is about to be merged or shipped.
+- You need a release readiness gate.
+- Scope, validation, rollback, or documentation still needs a final pass.
+
+## How
+
+- Verify readiness, blockers, and handoff items before the release is approved.
+- Confirm the change scope, test evidence, and rollout notes are aligned.
+- Call out any missing rollback, monitoring, or ownership detail.
+- Keep the result focused on release readiness, not implementation rewrites.
+
+## When to Avoid
+
+- The delivery is not ready yet.
+- You need to change code rather than document release steps.
+- The request is only a short change summary.

package/skills/05-delivery/release-check/assets/golden-prompt-suite.current.js

@@ -0,0 +1,22 @@
+#!/usr/bin/env node
+
+module.exports = {
+  "name": "release-check.golden-prompt-suite.current",
+  "skill": "release-check",
+  "description": "Confirm a change is ready for release with the required gates and evidence.",
+  "cases": [
+    {
+      "id": "release-readiness-check",
+      "prompt": "Before release, check readiness and blockers.",
+      "expectedFirstSkill": "release-check",
+      "expectedOutput": [
+        "release readiness",
+        "blockers",
+        "next actions"
+      ],
+      "expectedStop": "Do not start new feature work.",
+      "expectedHandoff": "release-validation"
+    }
+  ]
+};
+

package/skills/05-delivery/release-check/references/README.md

@@ -0,0 +1,17 @@
+# release-check References
+
+This directory is local to the skill and is the only reference entry point for this skill.
+
+## Contents
+
+- `../skill-spec.json`: design source for regenerating this skill
+- `prompt-template.md`: reusable prompt wording for this skill
+- `cases.md`: human-readable replay case for this skill
+- `../assets/golden-prompt-suite.current.js`: machine-readable local case fixture
+
+## Guidance
+
+- Keep skill-specific explanation here instead of pushing it into a stage-level shared library.
+- Keep shared hard constraints in `../../../rules/index.md`.
+- Keep canonical names unchanged.
+- Skill summary: Confirm a change is ready for release with the required gates and evidence.

package/skills/05-delivery/release-check/references/cases.md

@@ -0,0 +1,26 @@
+# release-check
+
+## Replay Case
+
+- Case: `release-readiness-check`
+- First skill: `release-check`
+
+### Prompt
+
+```text
+Before release, check readiness and blockers.
+```
+
+### Expected Output
+
+- release readiness
+- blockers
+- next actions
+
+### Stop Rule
+
+- Do not start new feature work.
+
+### Handoff
+
+- release-validation

package/skills/05-delivery/release-check/references/prompt-template.md

@@ -0,0 +1,18 @@
+# release-check
+
+## Prompt Template
+
+```text
+You are handling the release-check skill.
+Goal: Confirm a change is ready for release with the required gates and evidence
+Inputs: the request, supporting evidence, constraints, and existing repository facts.
+Output contract: release readiness, blockers, next actions.
+Stop rule: Do not start new feature work.
+Handoff: release-validation.
+Keep the response scoped to this stage and do not absorb the work of the next stage.
+```
+
+## Notes
+
+- Keep the template aligned with the local replay case and local assets.
+- Read `cases.md` for the matching replay example.

package/skills/05-delivery/release-check/skill-spec.json

@@ -0,0 +1,25 @@
+{
+  "group": "05-delivery",
+  "name": "release-check",
+  "description": "Confirm a change is ready for release with the required gates and evidence.",
+  "title": "Release Check",
+  "purpose": "Verify the change is release-ready from scope, risk, and evidence perspectives.",
+  "whenToUse": [
+    "A change is about to be merged or shipped.",
+    "You need a release readiness gate.",
+    "Scope, validation, rollback, or documentation still needs a final pass."
+  ],
+  "how": [
+    "Verify readiness, blockers, and handoff items before the release is approved.",
+    "Confirm the change scope, test evidence, and rollout notes are aligned.",
+    "Call out any missing rollback, monitoring, or ownership detail.",
+    "Keep the result focused on release readiness, not implementation rewrites."
+  ],
+  "whenToAvoid": [
+    "The delivery is not ready yet.",
+    "You need to change code rather than document release steps.",
+    "The request is only a short change summary."
+  ],
+  "caseId": "release-readiness-check",
+  "source": "bootstrap-from-skill-md"
+}