tenferro-issue-intake

Estrelas64

Forks2

Atualizado27 de maio de 2026 às 23:00

Create or refine tenferro-rs GitHub issues through a step-by-step intake workflow. Use for bug reports, feature requests, design discussion issues, documentation issues, article-topic issues, and when a user proposes a new feature PR that must be redirected to an issue first. Do not use for implementation work.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

tensor4all

tensor4all/tenferro-rs

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Desenvolvedores de softwareInformática e Matemática·SOC 15-1252

SKILL.md

readonly

name	tenferro-issue-intake
description	Create or refine tenferro-rs GitHub issues through a step-by-step intake workflow. Use for bug reports, feature requests, design discussion issues, documentation issues, article-topic issues, and when a user proposes a new feature PR that must be redirected to an issue first. Do not use for implementation work.

Tenferro Issue Intake

Follow ai/contribution-workflows/issue-intake.md as the canonical workflow.

Read that file before drafting. Ask the user only for missing judgment calls or facts that cannot be discovered from the repository or GitHub state.

Keep the interaction incremental:

Classify the issue type.
Collect the goal and current friction.
Gather reproduction details or use-case details.
Apply the contribution scope gate.
Draft title, body, acceptance criteria, and provenance notes.
Wait for confirmation before creating the issue unless the user explicitly asked for direct creation.

Mais deste repositório

mesmo repositório

tenferro-release-publish

tensor4all/tenferro-rs

Release a new tenferro-rs version. Use for workspace version bumps, tagging, crates.io publication in dependency order, and post-publish provenance verification. Publishing is irreversible and requires maintainer crates.io ownership. Do not use for ordinary feature or bug-fix PRs, and never publish from an unpushed or untagged commit.

2026-07-0464

tenferro-bugfix-pr

tensor4all/tenferro-rs

Prepare a tenferro-rs bug-fix PR for existing intended behavior. Use for regression fixes, panic fixes, wrong-result fixes, compatibility fixes, related bug batches, repository-rule audit findings, same-root-cause bug sweeps, and false-positive bug reports that need source comments or source-contract tests. Do not use for new features, new public APIs, new backends, new dependencies, feature flags, or architectural changes; redirect those to issue intake.

2026-06-1764

tenferro-bugfix-pr

tensor4all/tenferro-rs

2026-06-1764

tenferro-issue-intake

tensor4all/tenferro-rs

2026-05-2764

Execute qualquer Skill com um clique