@kernelius/openclaw-plugin 0.2.3 → 0.3.0

package/README.md

@@ -153,6 +153,36 @@ Example:
 }
 ```
 
+## Actions
+
+### Send Message
+Send a comment to an issue or PR:
+```javascript
+{
+  action: "send",
+  to: "repo:owner/name:issue:42",
+  message: "Your comment text"
+}
+```
+
+### React
+Add an emoji reaction to issues, PRs, or comments:
+```javascript
+{
+  action: "react",
+  messageId: "issue_comment:abc123",  // or issue:, pr:, pr_comment:
+  emoji: "+1"  // Valid: +1, -1, laugh, hooray, confused, heart, rocket, eyes
+}
+```
+
+**messageId formats:**
+- `issue:<id>` - React to an issue
+- `pr:<id>` - React to a pull request
+- `issue_comment:<id>` - React to an issue comment
+- `pr_comment:<id>` - React to a PR comment
+
+Inbound webhook messages include `messageId` automatically, allowing agents to react to incoming comments.
+
 ## Webhook Events
 
 The plugin handles these Forge webhook events:
@@ -168,6 +198,7 @@ The plugin handles these Forge webhook events:
 | `pr.updated` | PR title/body changed |
 | `pr.merged` | Pull request merged |
 | `pr.closed` | PR closed without merging |
+| `pr.reopened` | PR reopened |
 | `pr.review_requested` | Review requested on PR |
 | `pr.reviewed` | Review submitted |
 | `pr.commented` | Comment on PR |
@@ -210,6 +241,23 @@ npm run dev
 npm run typecheck
 ```
 
+## Bundled Skills
+
+This plugin includes OpenClaw skills for common Forge workflows:
+
+| Skill | Description |
+|-------|-------------|
+| [forge-issue-triager](./skills/forge-issue-triager/) | Auto-triage incoming issues |
+| [forge-code-reviewer](./skills/forge-code-reviewer/) | Review pull requests |
+| [forge-pr-summarizer](./skills/forge-pr-summarizer/) | Generate PR summaries |
+
+Install skills by copying to your OpenClaw skills directory:
+```bash
+cp -r node_modules/@kernelius/openclaw-plugin/skills/forge-issue-triager ~/.openclaw/skills/
+```
+
+See [skills/README.md](./skills/README.md) for details.
+
 ## Links
 
 - [Kernelius Forge](https://forge.kernelius.com)

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@kernelius/openclaw-plugin",
-  "version": "0.2.3",
+  "version": "0.3.0",
   "description": "OpenClaw channel plugin for Kernelius Forge - enables agents to work with repositories, issues, and pull requests",
   "type": "module",
   "main": "./dist/index.js",
@@ -13,6 +13,7 @@
   },
   "files": [
     "dist",
+    "skills",
     "README.md",
     "LICENSE"
   ],

package/skills/README.md

@@ -0,0 +1,67 @@
+# Kernelius Forge Skills
+
+OpenClaw skills for automating workflows with Kernelius Forge.
+
+## Available Skills
+
+| Skill | Description | Triggers |
+|-------|-------------|----------|
+| [forge-issue-triager](./forge-issue-triager/) | Triage issues automatically | `issue.created` |
+| [forge-code-reviewer](./forge-code-reviewer/) | Review pull requests | `pr.review_requested`, `pr.created` |
+| [forge-pr-summarizer](./forge-pr-summarizer/) | Generate PR summaries | `pr.created`, `pr.merged` |
+
+## Prerequisites
+
+These skills require:
+1. The `@kernelius/openclaw-plugin` channel configured
+2. The `forge` CLI installed (`npm install -g @kernelius/forge-cli`)
+3. Webhooks configured on your Forge repositories
+
+## Installation
+
+Copy the desired skill folder to your OpenClaw skills directory:
+
+```bash
+cp -r skills/forge-issue-triager ~/.openclaw/skills/
+```
+
+Or reference them directly in your OpenClaw configuration.
+
+## Usage with Webhooks
+
+These skills are designed to work with Forge webhooks. Configure webhook mappings in your OpenClaw `config.json5`:
+
+```json5
+{
+  channels: {
+    kernelius: {
+      enabled: true,
+      apiUrl: "https://forge-api.kernelius.com",
+      apiKey: "forge_agent_xxx...",
+      webhookPath: "/kernelius",
+      webhookSecret: "your-secret"
+    }
+  }
+}
+```
+
+Then create webhooks pointing to your OpenClaw instance:
+
+```bash
+forge webhooks create \
+  --repo @owner/repo \
+  --url "http://your-openclaw:18789/kernelius" \
+  --events "issue.created,pr.created,pr.review_requested,pr.merged" \
+  --secret "your-secret"
+```
+
+## Complementary Skills
+
+These skills work alongside the [forge CLI skill](https://github.com/your-openclaw/skills/forge) which provides direct CLI commands for Forge operations.
+
+## Contributing
+
+To add a new skill:
+1. Create a folder with your skill name
+2. Add a `SKILL.md` with proper frontmatter
+3. Follow the [OpenClaw skill guidelines](https://openclaw.dev/docs/skills)

package/skills/forge-code-reviewer/SKILL.md

@@ -0,0 +1,237 @@
+---
+name: forge-code-reviewer
+description: "Review pull requests on Kernelius Forge. Triggered by pr.review_requested or pr.created webhooks. Analyze code changes, check for issues, and submit reviews. Use when receiving PR review requests from Forge."
+metadata:
+  {
+    "openclaw":
+      {
+        "emoji": "🔍",
+        "requires": { "channels": ["kernelius"], "bins": ["forge"] },
+      },
+  }
+---
+
+# Forge Code Reviewer
+
+Automatically review pull requests from Kernelius Forge. Analyze diffs, identify issues, and submit constructive reviews.
+
+## Webhook Triggers
+
+- `pr.review_requested` - Someone requested your review
+- `pr.created` - New PR opened (if configured to auto-review)
+
+## Review Workflow
+
+### 1. Gather PR Information
+
+Use the forge CLI to get details:
+
+```bash
+# View PR details
+forge prs view --repo @owner/repo --number 10
+
+# View the diff
+forge prs diff --repo @owner/repo --number 10
+
+# List commits
+forge prs commits --repo @owner/repo --number 10
+```
+
+### 2. Analyze the Changes
+
+Check for:
+
+**Code Quality**
+- Clear, readable code
+- Appropriate naming conventions
+- No unnecessary complexity
+- Proper error handling
+
+**Correctness**
+- Logic errors
+- Edge cases handled
+- Type safety
+- Null/undefined checks
+
+**Security**
+- Input validation
+- SQL injection risks
+- XSS vulnerabilities
+- Sensitive data exposure
+- Authentication/authorization
+
+**Performance**
+- Unnecessary loops/iterations
+- N+1 query patterns
+- Memory leaks
+- Blocking operations
+
+**Tests**
+- Test coverage for new code
+- Edge cases tested
+- Tests are meaningful
+
+**Documentation**
+- Comments for complex logic
+- API documentation updated
+- README updated if needed
+
+### 3. Submit Review
+
+Use the forge CLI to submit:
+
+```bash
+# Approve
+forge prs review --repo @owner/repo --number 10 \
+  --state approve \
+  --body "LGTM! Code looks good."
+
+# Request changes
+forge prs review --repo @owner/repo --number 10 \
+  --state request_changes \
+  --body "Please address the issues below."
+
+# Comment only
+forge prs review --repo @owner/repo --number 10 \
+  --state comment \
+  --body "Some observations..."
+```
+
+Or comment via the channel:
+
+```
+action: send
+to: repo:owner/name:pr:10
+message: |
+  ## Code Review
+
+  ### Summary
+  {Overall assessment}
+
+  ### Issues Found
+  {List of issues}
+
+  ### Suggestions
+  {Improvements}
+```
+
+## Review Templates
+
+### Approval
+
+```markdown
+## ✅ Code Review: Approved
+
+### Summary
+Clean implementation of {feature}. Code is well-structured and follows project conventions.
+
+### Highlights
+- Good error handling in {file}
+- Clear separation of concerns
+- Tests cover the main scenarios
+
+### Minor Suggestions (non-blocking)
+- Consider extracting {function} for reusability
+- Could add a comment explaining {complex logic}
+
+---
+🤖 Reviewed by OpenClaw
+```
+
+### Request Changes
+
+```markdown
+## 🔄 Code Review: Changes Requested
+
+### Summary
+Good progress on {feature}, but some issues need addressing before merge.
+
+### Required Changes
+
+#### 1. {Issue Title}
+**File:** `{path/to/file.ts}`
+**Line:** {line number}
+
+{Description of the issue and why it matters}
+
+**Suggested fix:**
+```{language}
+{code suggestion}
+```
+
+#### 2. {Issue Title}
+...
+
+### Questions
+- {Any clarifying questions}
+
+---
+🤖 Reviewed by OpenClaw
+```
+
+### Comment Only
+
+```markdown
+## 💬 Code Review Notes
+
+### Observations
+{General observations about the PR}
+
+### Questions
+- {Questions about approach or implementation}
+
+### Suggestions
+- {Non-blocking suggestions}
+
+I'll wait for clarification before making a final decision.
+
+---
+🤖 Reviewed by OpenClaw
+```
+
+## Common Issues to Flag
+
+### Security
+- `// TODO: validate input` - Flag incomplete validation
+- Hardcoded credentials or secrets
+- SQL string concatenation
+- `dangerouslySetInnerHTML` without sanitization
+- Missing authentication checks
+
+### Performance
+- `await` inside loops (could be `Promise.all`)
+- Fetching all records without pagination
+- Missing database indexes for queried fields
+- Synchronous file operations
+
+### Code Quality
+- Functions over 50 lines
+- Deeply nested conditionals (>3 levels)
+- Magic numbers without constants
+- Inconsistent error handling
+- Dead code or unused imports
+
+## Reactions
+
+Acknowledge the review request:
+```
+action: react
+messageId: pr:{pr-id}
+emoji: eyes
+```
+
+After reviewing:
+```
+action: react
+messageId: pr:{pr-id}
+emoji: +1  # or -1 if changes needed
+```
+
+## Best Practices
+
+1. **Be constructive** - Explain *why*, not just *what*
+2. **Prioritize feedback** - Distinguish blocking vs nice-to-have
+3. **Provide examples** - Show the suggested fix when possible
+4. **Acknowledge good work** - Mention things done well
+5. **Ask questions** - If unsure, ask rather than assume
+6. **Be timely** - Review promptly to unblock the author

package/skills/forge-issue-triager/SKILL.md

@@ -0,0 +1,179 @@
+---
+name: forge-issue-triager
+description: "Triage Kernelius Forge issues automatically. Triggered by issue.created webhooks. Analyze issues, suggest priority/labels, assign to teams, and respond with actionable guidance. Use when receiving new issue notifications from Forge."
+metadata:
+  {
+    "openclaw":
+      {
+        "emoji": "🏷️",
+        "requires": { "channels": ["kernelius"] },
+      },
+  }
+---
+
+# Forge Issue Triager
+
+Automatically triage issues from Kernelius Forge webhooks. Analyze content, determine priority, suggest labels, and respond with helpful guidance.
+
+## Webhook Trigger
+
+This skill activates when you receive an `issue.created` webhook from Forge. The inbound message contains:
+
+- Issue title and body
+- Repository context
+- Author information
+- Conversation target for replies
+
+## Triage Workflow
+
+### 1. Analyze the Issue
+
+Extract key information:
+- **Type**: Bug report, feature request, question, documentation
+- **Severity**: Critical (production down), high (major functionality), medium (workflow impact), low (minor/cosmetic)
+- **Component**: Which part of the system is affected
+- **Reproducibility**: Can it be reproduced? Steps provided?
+
+### 2. Determine Priority
+
+| Priority | Criteria |
+|----------|----------|
+| P0 | Production outage, security vulnerability, data loss |
+| P1 | Major feature broken, no workaround |
+| P2 | Feature degraded, workaround exists |
+| P3 | Minor issue, cosmetic, enhancement |
+
+### 3. Suggest Labels
+
+Common label categories:
+- Type: `bug`, `feature`, `question`, `docs`
+- Priority: `priority:critical`, `priority:high`, `priority:medium`, `priority:low`
+- Status: `needs-triage`, `needs-info`, `confirmed`, `wontfix`
+- Component: `api`, `web`, `mobile`, `database`, `auth`
+
+### 4. Respond to the Issue
+
+Use the channel's messaging to comment on the issue:
+
+```
+action: send
+to: repo:owner/name:issue:42
+message: |
+  ## Triage Summary
+
+  **Type:** Bug Report
+  **Priority:** P2 (Medium)
+  **Component:** Authentication
+
+  ### Analysis
+  [Your analysis of the issue]
+
+  ### Suggested Labels
+  - `bug`
+  - `priority:medium`
+  - `auth`
+
+  ### Next Steps
+  - [ ] Reproduce the issue
+  - [ ] Identify root cause
+  - [ ] Propose fix
+
+  ---
+  🤖 Auto-triaged by OpenClaw
+```
+
+## Response Templates
+
+### Bug Report Response
+
+```markdown
+## Triage Summary
+
+**Type:** 🐛 Bug Report
+**Priority:** {P0|P1|P2|P3}
+**Component:** {component}
+
+### Analysis
+{Brief analysis of the bug and its impact}
+
+### Information Needed
+{If applicable, what additional info is needed}
+
+### Suggested Labels
+- `bug`
+- `priority:{level}`
+- `{component}`
+
+---
+🤖 Auto-triaged by OpenClaw
+```
+
+### Feature Request Response
+
+```markdown
+## Triage Summary
+
+**Type:** ✨ Feature Request
+**Priority:** {P2|P3}
+
+### Analysis
+{Brief analysis of the feature request}
+
+### Considerations
+- Use case validity
+- Implementation complexity
+- Alignment with roadmap
+
+### Suggested Labels
+- `feature`
+- `priority:{level}`
+- `needs-discussion`
+
+---
+🤖 Auto-triaged by OpenClaw
+```
+
+### Question Response
+
+```markdown
+## Response
+
+{Direct answer to the question if possible}
+
+### Resources
+- [Link to relevant docs]
+- [Related issues]
+
+### Suggested Labels
+- `question`
+- `{topic}`
+
+---
+🤖 Answered by OpenClaw
+```
+
+## Reactions
+
+Add a reaction to acknowledge you've seen the issue:
+
+```
+action: react
+messageId: issue:{issue-id}
+emoji: eyes
+```
+
+After triaging:
+
+```
+action: react
+messageId: issue:{issue-id}
+emoji: +1
+```
+
+## Best Practices
+
+1. **Be helpful, not bureaucratic** - Focus on moving the issue forward
+2. **Ask clarifying questions** - If info is missing, ask specifically what's needed
+3. **Provide context** - Explain why you assigned the priority/labels
+4. **Link related issues** - Help identify duplicates or related work
+5. **Set expectations** - Give a realistic sense of timeline if known

package/skills/forge-pr-summarizer/SKILL.md

@@ -0,0 +1,211 @@
+---
+name: forge-pr-summarizer
+description: "Generate summaries for Kernelius Forge pull requests. Triggered by pr.created or pr.merged webhooks. Create changelogs, release notes, and PR descriptions. Use when needing to summarize PR changes."
+metadata:
+  {
+    "openclaw":
+      {
+        "emoji": "📝",
+        "requires": { "channels": ["kernelius"], "bins": ["forge"] },
+      },
+  }
+---
+
+# Forge PR Summarizer
+
+Generate clear, helpful summaries for pull requests. Create changelogs, release notes, and improve PR descriptions.
+
+## Webhook Triggers
+
+- `pr.created` - Summarize new PRs
+- `pr.merged` - Generate changelog entries
+
+## Summary Workflow
+
+### 1. Gather PR Information
+
+```bash
+# Get PR details
+forge prs view --repo @owner/repo --number 10
+
+# Get the diff
+forge prs diff --repo @owner/repo --number 10
+
+# Get commits
+forge prs commits --repo @owner/repo --number 10
+```
+
+### 2. Analyze Changes
+
+Categorize changes:
+- **Features** - New functionality
+- **Fixes** - Bug fixes
+- **Refactoring** - Code improvements without behavior change
+- **Docs** - Documentation updates
+- **Tests** - Test additions/modifications
+- **Chores** - Dependencies, config, tooling
+
+### 3. Generate Summary
+
+Post summary as a comment:
+
+```
+action: send
+to: repo:owner/name:pr:10
+message: |
+  ## PR Summary
+
+  {Generated summary}
+```
+
+## Summary Templates
+
+### PR Description Enhancement
+
+```markdown
+## Summary
+{One-line summary of what this PR does}
+
+## Changes
+- {Change 1}
+- {Change 2}
+- {Change 3}
+
+## Type
+- [ ] Feature
+- [ ] Bug fix
+- [ ] Refactor
+- [ ] Documentation
+- [ ] Test
+- [ ] Chore
+
+## Testing
+{How to test these changes}
+
+## Screenshots
+{If applicable}
+
+---
+📝 Summary by OpenClaw
+```
+
+### Changelog Entry (for merged PRs)
+
+```markdown
+## Changelog Entry
+
+### {Version or Date}
+
+#### Added
+- {New feature from this PR}
+
+#### Changed
+- {Modified behavior}
+
+#### Fixed
+- {Bug that was fixed}
+
+#### Removed
+- {Deprecated features removed}
+
+---
+📝 Generated by OpenClaw
+```
+
+### Release Notes
+
+```markdown
+## Release Notes
+
+### {Feature/Fix Title}
+
+{User-facing description of the change}
+
+**What's new:**
+- {Benefit 1}
+- {Benefit 2}
+
+**Migration notes:**
+{If any breaking changes or migration steps needed}
+
+---
+📝 Generated by OpenClaw
+```
+
+### Technical Summary
+
+```markdown
+## Technical Summary
+
+### Files Changed
+| File | Changes |
+|------|---------|
+| `{path}` | {description} |
+
+### Key Changes
+
+#### {Component 1}
+{Technical details of changes}
+
+#### {Component 2}
+{Technical details of changes}
+
+### Dependencies
+- Added: {new deps}
+- Removed: {removed deps}
+- Updated: {updated deps}
+
+### Database Changes
+{If any schema changes}
+
+### API Changes
+{If any endpoint changes}
+
+---
+📝 Generated by OpenClaw
+```
+
+## Commit Message Analysis
+
+Parse commit messages to understand changes:
+
+```
+feat: Add user authentication
+^     ^
+|     |__ Description
+|__ Type
+```
+
+Common prefixes:
+- `feat:` - New feature
+- `fix:` - Bug fix
+- `docs:` - Documentation
+- `style:` - Formatting
+- `refactor:` - Code restructuring
+- `test:` - Tests
+- `chore:` - Maintenance
+
+## Best Practices
+
+1. **User-focused language** - Explain what users get, not just what code changed
+2. **Be concise** - Summarize, don't repeat the entire diff
+3. **Highlight breaking changes** - Make them prominent
+4. **Group related changes** - Organize by feature/component
+5. **Link to issues** - Reference related issues/discussions
+6. **Include context** - Why was this change made?
+
+## Reactions
+
+Acknowledge you're generating a summary:
+```
+action: react
+messageId: pr:{pr-id}
+emoji: eyes
+```
+
+After posting summary:
+```
+action: react
+messageId: pr:{pr-id}
+emoji: rocket
+```