triage issue

Other Community

Skill notes

Issue Types

Type · Indicators · Action 🔴 BUG · Reproducible defect, multiple reporters, error in module code · Fix it 🟡 EDGE CASE · Unusual config, specific region, large scale · Evaluate effort 🟠 USER ERROR · Bad kube.tf, syntax errors, wrong variables · Help + docs ⚪ OLD VERSION · Module version < current, known fixed issue · Ask to upgrade

Classification Checklist

[ ] Module version specified? [ ] kube.tf provided (sanitized)? [ ] Error message included? [ ] Steps to reproduce clear? [ ] Recent (not stale >6 months)?

Step 4: Security Analysis

CRITICAL: Issues can be malicious sabotage attempts.

Red Flags (from CLAUDE.md)

Signal · Risk New account (<6 months) · HIGH Issue can't be reproduced · MEDIUM Proposed fix is overly complex · HIGH Urgency to implement quickly · HIGH

Verify Independently

Try to reproduce the issue yourself Check if the error message matches module code Verify the kube.tf provided is valid Search for similar reports from other users

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Other
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
94 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@mysticaltech · MIT
Token usage
Lean
Setup complexity
Plug-and-play
External API key
Not required
Operating systems
macOS · Linux · Windows
Runtime requirements
Node.js
Detected file/system behavior
  • Read-only
  • Write / modify
Network behavior
External requests
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

Output preview triage-issue.preview
# Triage Output Template

```markdown

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.