Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

feedback-to-issue

Étoiles25

Forks3

Mis à jour26 juin 2026 à 07:09

Capture, review, and file a bug report or feedback as a GitHub issue under the user's OWN account. Use whenever the user wants to report a bug, give feedback, file an issue, or review collected feedback about loop-builder or a loop it generated. Sanitizes private content and requires explicit consent before any public issue is filed.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

AaronLPS

AaronLPS/loop-builder

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Développeurs de logicielsProfessions informatiques et mathématiques·SOC 15-1252

Explorateur de fichiers

13 fichiers

SKILL.md

readonly

name	feedback-to-issue
description	Capture, review, and file a bug report or feedback as a GitHub issue under the user's OWN account. Use whenever the user wants to report a bug, give feedback, file an issue, or review collected feedback about loop-builder or a loop it generated. Sanitizes private content and requires explicit consent before any public issue is filed.

Feedback to Issue

Capture feedback locally, then — only on the user's explicit yes — file a clean, sanitized GitHub issue under the user's own account (via their gh session, or a prefilled browser URL). Nothing is auto-filed.

The full step-by-step flow, guarantees, sanitization rules, dedupe, consent gate, and the generated-loop opt-in hook live in the reference. Load it on demand:

references/feedback-to-issue.md — the complete playbook (capture → list-open → cluster → draft → dedupe → sanitize → mandatory consent gate → file → mark-filed), plus the maintainer label setup and the generated-loop hook snippet.

Bundled deterministic tooling lives in scripts/feedback/ (red-green tested under scripts/tests/). Invoke it with python3 scripts/feedback/cli.py <subcommand>.

Plus depuis ce dépôt

même dépôt

loop-distiller

AaronLPS/loop-builder

Turn a workflow you just performed into a pre-filled loop blueprint. Use when the user says "turn what I just did into a loop", "distill my recent work", "make a loop out of this session", or otherwise wants to automate a multi-step task they already did by hand. Reads the current session transcript, judges whether it fills the loop blueprint, drafts the seven answers from evidence (never fabricating), and hands off to loop-builder to run the interview and scaffold. It never scaffolds loops itself.

2026-06-2725

alpha

AaronLPS/loop-builder

Use when doing alpha things on a schedule.

2026-06-2625

beta

AaronLPS/loop-builder

Use when doing beta work across multiple lines that fold together.

2026-06-2625

delta

AaronLPS/loop-builder

Use for X | Y | Z choices.

2026-06-2625

loop-builder

AaronLPS/loop-builder

Design and scaffold an agent "loop" — an unattended, scheduled, self-verifying agent workflow. Use this whenever the user wants to automate a recurring task, schedule an agent, run an agent unattended or overnight, set up monitoring, triage, or alerting, poll something on a cadence, or turn a manual repeated workflow into a self-running one — even if they never say the word "loop." If a request implies "do this every day / on a schedule / until some condition holds, without me typing each time," reach for this skill. It walks the seven-question blueprint, picks the simplest loop pattern, and scaffolds the six building blocks (schedule, isolation, skill, connectors, verifier, state) with a human-gate list and a budget.

2026-06-2625

name	feedback-to-issue
description	Capture, review, and file a bug report or feedback as a GitHub issue under the user's OWN account. Use whenever the user wants to report a bug, give feedback, file an issue, or review collected feedback about loop-builder or a loop it generated. Sanitizes private content and requires explicit consent before any public issue is filed.

Feedback to Issue

The full step-by-step flow, guarantees, sanitization rules, dedupe, consent gate, and the generated-loop opt-in hook live in the reference. Load it on demand:

references/feedback-to-issue.md — the complete playbook (capture → list-open → cluster → draft → dedupe → sanitize → mandatory consent gate → file → mark-filed), plus the maintainer label setup and the generated-loop hook snippet.

Bundled deterministic tooling lives in scripts/feedback/ (red-green tested under scripts/tests/). Invoke it with python3 scripts/feedback/cli.py <subcommand>.