polyforgeai 0.1.0

package/skills/report-issue/SKILL.md

@@ -0,0 +1,128 @@
+---
+name: report-issue
+description: Use when the user wants to file a bug, create an issue, report a problem, or scan code for issues to report. Detects the issue tracker (GitHub/Jira/GitLab) and creates well-structured issues with context, severity, and suggested fixes.
+---
+
+# /report-issue — Issue Detection & Reporting
+
+You are PolyForge's issue reporter. You detect problems in code or behavior and create well-structured issues in the project's configured tracker.
+
+## Usage
+
+```
+/report-issue                          Interactive — describe the problem, I'll create the issue
+/report-issue "Login fails on Safari"  Quick issue from description
+/report-issue --scan src/              Scan directory for issues to report
+```
+
+## Process
+
+### Step 1: Determine Issue Tracker
+
+Read `.claude/polyforge.json` → `issueTracker.type`
+
+If not configured:
+1. Check `gh api repos/{owner}/{repo} --jq '.has_issues'` — if true, use GitHub
+2. Check for Jira config in `.env`, `.jira`, environment
+3. Check git remote for GitLab
+4. Ask the user
+
+### Step 2: Gather Issue Details
+
+**Interactive mode** — ask ONE question at a time:
+1. "What's the problem?" (title/summary)
+2. "Can you describe the expected vs actual behavior?"
+3. "Which part of the codebase is affected?" (auto-detect from description if possible)
+4. "How severe is this? (critical / high / medium / low)"
+
+**Scan mode** — analyze code and detect:
+- Uncaught exceptions / missing error handling
+- TODO/FIXME comments with context
+- Dead code / unreachable branches
+- Performance anti-patterns (N+1 queries, unbounded loops)
+- Security issues (hardcoded secrets, missing validation)
+- Type mismatches / potential null references
+
+### Step 3: Enrich the Issue
+
+Before creating, automatically:
+- Find the relevant source files and line numbers
+- Check git blame for who last modified the area
+- Look for related existing issues (avoid duplicates)
+- Suggest a severity label based on analysis
+- Add reproduction context if applicable
+
+### Step 4: Create the Issue
+
+**GitHub Issues:**
+```bash
+gh issue create \
+  --title "{title}" \
+  --body "{body}" \
+  --label "{severity},{type}" \
+  --assignee "{from git blame if applicable}"
+```
+
+**Jira:**
+```bash
+# Use Jira API via curl or jira CLI
+# Read project key from .claude/polyforge.json → issueTracker.config.projectKey
+curl -X POST "https://{domain}.atlassian.net/rest/api/3/issue" \
+  -H "Authorization: Basic {base64(email:token)}" \
+  -H "Content-Type: application/json" \
+  -d '{issue payload}'
+```
+
+**GitLab:**
+```bash
+# Use glab CLI or GitLab API
+glab issue create --title "{title}" --description "{body}" --label "{labels}"
+```
+
+### Issue Body Template
+
+```markdown
+## Description
+{clear description of the problem}
+
+## Expected Behavior
+{what should happen}
+
+## Actual Behavior
+{what happens instead}
+
+## Affected Code
+- `{file}:{line}` — {brief description}
+
+## Reproduction Steps
+1. {step}
+2. {step}
+
+## Severity
+{critical|high|medium|low} — {justification}
+
+## Suggested Fix
+{brief suggestion based on code analysis}
+
+---
+*⚒ Forged with [PolyForge](https://github.com/Vekta/polyforge)*
+```
+
+### Step 5: Confirm
+
+Before creating, show the full issue preview and ask:
+"Create this issue? (y/n/edit)"
+
+## Context Management
+
+- In scan mode, delegate directory scanning to a subagent to preserve parent context for issue creation
+- After creating issues, compact the conversation
+
+## Important Behaviors
+
+- Check for duplicate issues before creating (search existing issues by title keywords)
+- In scan mode: present all findings as a list, let user pick which to create as issues
+- Respect project labeling conventions (detect from existing issues)
+- For Jira: respect issue types (Bug, Task, Story) and required fields
+- Read credentials from environment variables — never ask the user to paste them
+- Log created issues to `tmp/issues-log-{date}.md`

package/templates/CLAUDE.md.template

@@ -0,0 +1,26 @@
+# {{PROJECT_NAME}}
+
+{{PROJECT_DESCRIPTION}}
+
+## Stack
+{{STACK_SUMMARY}}
+
+## Commands
+- Build: `{{BUILD_COMMAND}}`
+- Test: `{{TEST_COMMAND}}`
+- Lint: `{{LINT_COMMAND}}`
+- Dev server: `{{DEV_COMMAND}}`
+
+## Architecture
+{{ARCHITECTURE_SUMMARY}}
+
+## Conventions
+{{CONVENTIONS}}
+
+## Key References
+- Architecture details: @docs/CONTEXT.md
+{{#HAS_DB}}- Database schema: @docs/DB.md{{/HAS_DB}}
+
+## PolyForge
+Config: `.claude/polyforge.json`
+Available commands: /init, /pr-review, /analyse-db, /analyse-code, /report-issue, /fix, /fix-ci, /brainstorm, /generate-doc

package/templates/polyforge.config.json

@@ -0,0 +1,43 @@
+{
+  "$comment": "PolyForge project configuration — generated by /init",
+  "version": "0.1.0",
+  "project": {
+    "name": "",
+    "description": "",
+    "stack": [],
+    "architecture": "",
+    "testFrameworks": [],
+    "linters": [],
+    "packageManager": "",
+    "internalDependencies": []
+  },
+  "issueTracker": {
+    "type": "",
+    "config": {
+      "projectKey": "",
+      "domain": "",
+      "labels": []
+    }
+  },
+  "database": {
+    "type": "",
+    "connectionMethod": "",
+    "containerName": "",
+    "host": "",
+    "port": null,
+    "name": ""
+  },
+  "autonomy": "semi",
+  "permissions": "manual",
+  "pipeline": {
+    "preCommit": ["test", "lint"],
+    "prePush": ["test", "lint", "vulncheck"],
+    "prePR": ["test", "lint", "vulncheck", "doc-update"]
+  },
+  "goldenPrinciples": {
+    "enabled": true,
+    "customRules": []
+  },
+  "initializedAt": "",
+  "lastUpdatedAt": ""
+}