@armstrongnate/april 0.0.1

package/package.json

@@ -0,0 +1,33 @@
+{
+  "name": "@armstrongnate/april",
+  "version": "0.0.1",
+  "description": "She does all the work so you don't have to. Watches GitHub issues and spawns Claude Code sessions to work them.",
+  "type": "module",
+  "bin": {
+    "april": "./dist/cli.js"
+  },
+  "files": [
+    "dist",
+    "skills",
+    "config.example.yaml",
+    "README.md"
+  ],
+  "scripts": {
+    "build": "tsc",
+    "dev": "tsx src/index.ts",
+    "start": "node dist/index.js",
+    "prepublishOnly": "pnpm build"
+  },
+  "engines": {
+    "node": ">=22.0.0"
+  },
+  "dependencies": {
+    "fastify": "^5.8.4",
+    "yaml": "^2.8.3"
+  },
+  "devDependencies": {
+    "@types/node": "^25.5.2",
+    "tsx": "^4.21.0",
+    "typescript": "^6.0.2"
+  }
+}

package/skills/issue-worker/SKILL.md

@@ -0,0 +1,53 @@
+---
+name: issue-worker
+description: Autonomously work a GitHub issue end-to-end — read, implement, and open a PR with no human input required.
+---
+
+# issue-worker
+
+You have been assigned a GitHub issue. Work it to completion autonomously. Do not stop to ask for approval or confirmation — go straight from reading the issue to opening a PR.
+
+## 1. Read the issue
+
+```
+gh issue view {issue_number} --repo {owner}/{repo} --comments
+```
+
+## 2. Understand the context
+
+- Read CLAUDE.md for project conventions
+- Identify relevant files and existing patterns
+- Check for existing tests covering the affected code
+
+## 3. Implement
+
+- Make the changes
+- Write or update tests as appropriate
+- Ensure the code builds/lints/passes tests
+
+## 4. Review and simplify
+
+Run `git diff` and review your own changes. Fix any issues before committing.
+
+- **Correctness:** Does it fully address the issue? Missing edge cases?
+- **Simplify:** Can anything be combined, inlined, or removed? Prefer fewer files, less indirection, and no unnecessary abstractions.
+- **Reuse:** Are you duplicating logic that already exists in the codebase? Use existing helpers and patterns.
+- **Cleanup:** Remove leftover debug code, TODOs, unused imports, and dead code.
+- **Style:** Match the conventions of the surrounding code.
+- **Tests:** Are the tests meaningful, not just testing mocks?
+
+## 5. Commit, push, and open a PR
+
+```
+gh pr create --title "..." --body "..."
+```
+
+Then update the issue labels:
+
+```
+gh issue edit {issue_number} --repo {owner}/{repo} --add-label agent:review --remove-label agent:wip
+```
+
+## 6. Post to Slack (if instructed)
+
+If the prompt specifies a Slack channel, use the Slack MCP tool to post a message with a link to the PR. Format: `<pr_url|PR> title of the pr`