anbeime/skill / skills/img2threejs/img2threejs
img2threejs
VerifiedTurn an object or character reference image into a quality-gated, animation-ready procedural Three.js model built in code. Use for image-to-3D reconstruction, detail-accurate object rebuilds, stylized/likeness-maximized human characters, sculpt specs, and staged code generation.
docs/issue-triage.md
View on GitHub# Issue triage
The triage workflow starts daily at 09:17 UTC and runs its helper on every second UTC epoch day, so
the cadence stays continuous across month boundaries. It is best effort, not an exact 48-hour
service level. A maintainer can use **Run workflow** in dry-run mode to see every zero-label
candidate, then use backfill only after reviewing that result. Scheduled runs consider only issues
created after `TRIAGE_ROLLOUT_AFTER` in `.github/workflows/issue-triage.yml`.
## Labels
| Axis | Labels | Owner |
| --- | --- | --- |
| Queue | `triage: needs-review`, `triage: discussed` | Bot adds only `needs-review`; maintainers transition it after discussion. |
| Priority | `priority: high`, `priority: medium`, `priority: low` | Maintainer, after a decision comment. |
| Contribution | `contribution: proposed`, `contribution: available`, `contribution: claimed` | The form adds `proposed`; maintainers control target-issue availability and claims. |
Existing labels such as `bug`, `enhancement`, and `documentation` remain independent. The bot never
removes labels, closes issues, locks them, assigns people, or applies terminal labels.
The scheduled candidate set is open non-PR issues with zero labels. The only exception is recovery
of an issue carrying exactly `triage: needs-review` when a prior bot run added that label but failed
before it could create the notice. A bot notice marker is accepted only from `github-actions[bot]`.
## Maintainer decision record
Before changing priority, contributor state, or closure, comment with the decision, rationale, next
action, and a revisit trigger if the issue becomes low priority. Low-priority issues remain open.
Implementation PRs use `Refs #<number>`. After merge, a maintainer records the merged PR,
verification, and closure rationale in the issue, then closes manually when appropriate.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |