Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

tlaplus-contribution

Estrelas0

Forks0

Atualizado15 de junho de 2026 às 22:10

Follow the tlaplus/tlaplus contribution conventions - engage maintainers early, make surgical diffs, write tests first, split PRs, use commit categorization tags and DCO sign-off. Use before any edit or PR, when authoring tests/docs, or crafting commit messages for this repo. For the mechanics of building/running tests see tlaplus-build-workflow.

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

jackfoxy

jackfoxy/foxy-skills

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

Explorador de arquivos

4 arquivos

SKILL.md

readonly

name	tlaplus-contribution
description	Follow the tlaplus/tlaplus contribution conventions - engage maintainers early, make surgical diffs, write tests first, split PRs, use commit categorization tags and DCO sign-off. Use before any edit or PR, when authoring tests/docs, or crafting commit messages for this repo. For the mechanics of building/running tests see tlaplus-build-workflow.
user-invocable	true
disable-model-invocation	false

Contributing to tlaplus/tlaplus

TL;DR (from CONTRIBUTING.md): engage maintainers early & often, be surgical, write lots of tests. TLA+ validates safety-critical systems, so quality gates are strict — a large surprise PR is very unlikely to be merged. Build/test commands: [[tlaplus-build-workflow]].

Process

Engage first. Comment on an existing issue or open one before coding; join the monthly meeting / mailing list for substantial work. Agree on scope, touched code, and required tests.
Fork → branch → PR against upstream master. (Run CI on your own by PRing within your fork.)
Write tests first. Good existing coverage of the changed area is a prerequisite to merge; prefer submitting tests as a separate PR so they land immediately.
Be surgical. Smallest diff that does the job; don't restyle unrelated code (keeps diffs reviewable/bisectable).
Split changes. Several small PRs > one large PR.
Craft commits. Treat commits as communication; ideally build & tests pass on every commit (amend rather than pile up check-ins — git tips in DEVELOPING.md).

Commits & sign-off (essentials)

Tag commits [Type][Component] (e.g. [Bug][TLC], add [Changelog] if notable) and always sign off:

git commit -s -am "message"     # -s = DCO Signed-off-by (required; CI enforces)

Full tag list, an example message, the DCO rationale, Java style guidance, and where-to-find-work are in references/commits-and-style.md.

Minimal acceptable PR (review checklist)

Linked issue with maintainer agreement.
Small, focused diff; nearby style matched.
New/updated unit test (or test-model/ spec+.cfg) covering the change — ideally a tests-first PR.
ant ... compile compile-test dist test passes ([[tlaplus-build-workflow]]).
Commit with [Type][Component] tags + -s DCO sign-off.

Validation

For a proposed change: name the issue to engage, the smallest diff, the test to add first, the commit tags, and confirm -s is present — before opening the PR.

References (local)

references/commits-and-style.md — commit tags, DCO, Java style, where to find work
CONTRIBUTING.md, DEVELOPING.md (git + style sections), general/docs/contributions.md, .github/CODE_OF_CONDUCT.md

Mais deste repositório

mesmo repositório

gviz-dot-syntax

jackfoxy/foxy-skills

Complete reference for the Graphviz DOT language — grammar, statements, identifiers, graph/node/edge/subgraph attributes, colors, ports, engines, and lexical edge cases — as accepted by the pure-Hoon %graph-viz renderer.

2026-07-100

gviz-gall-api

jackfoxy/foxy-skills

API reference for the %graph-viz Gall agent — the stateless subscribe-then-poke protocol, %gviz-command/%gviz-result marks, $command/$render-opts/$result/$err/$diag types, the run:lib gate, and the positioned-graph noun.

2026-07-100

gviz-patterns

jackfoxy/foxy-skills

Practical recipes and best practices for %graph-viz — rendering from Hoon, building graphs programmatically, worked diagram templates (org charts, dependency/architecture/state/data-flow/UML), styling and accessibility guidance, performance limits, pitfalls, integration (clay/caching), and debugging with verbose diagnostics.

2026-07-100

tlaplus-overview

jackfoxy/foxy-skills

High-level orientation to the tlaplus/tlaplus repository (TLA+ CLI tools + Eclipse Toolbox IDE), its tool entrypoints, and which sibling skill to use for a given task. Use when first interacting with the TLA+ toolchain repo, deciding between CLI/editor/build paths, or routing to the right tlaplus-* skill. Points to the shared external-link inventory and source-map for the whole pack.

2026-06-170

tlaplus-build-workflow

jackfoxy/foxy-skills

Build, package, test, and develop the TLA+ tools and Toolbox locally or in CI - Ant targets for tla2tools.jar, Maven/Tycho for the Toolbox, the test-set/test targets, the devcontainer, and the GitHub CI matrix. Use to compile the jar, run the test suite or a single test, set up a dev environment, or understand the CI pipeline. Owns every ant/mvn command line for the pack.

2026-06-150

tlaplus-debugging

jackfoxy/foxy-skills

Diagnose and recover from TLA+ failures - parse/level errors, config (.cfg) errors, TLC runtime errors, safety (invariant) and liveness violations, deadlock, and out-of-memory; analyze counterexample traces. Use for any SANY/TLC failure, opaque error, or trace/counterexample work. Owns the TLC/SANY error-code taxonomy for the pack.

2026-06-150

name	tlaplus-contribution
description	Follow the tlaplus/tlaplus contribution conventions - engage maintainers early, make surgical diffs, write tests first, split PRs, use commit categorization tags and DCO sign-off. Use before any edit or PR, when authoring tests/docs, or crafting commit messages for this repo. For the mechanics of building/running tests see tlaplus-build-workflow.
user-invocable	true
disable-model-invocation	false

Contributing to tlaplus/tlaplus

Process

Engage first. Comment on an existing issue or open one before coding; join the monthly meeting / mailing list for substantial work. Agree on scope, touched code, and required tests.
Fork → branch → PR against upstream master. (Run CI on your own by PRing within your fork.)
Write tests first. Good existing coverage of the changed area is a prerequisite to merge; prefer submitting tests as a separate PR so they land immediately.
Be surgical. Smallest diff that does the job; don't restyle unrelated code (keeps diffs reviewable/bisectable).
Split changes. Several small PRs > one large PR.
Craft commits. Treat commits as communication; ideally build & tests pass on every commit (amend rather than pile up check-ins — git tips in DEVELOPING.md).

Commits & sign-off (essentials)

Tag commits [Type][Component] (e.g. [Bug][TLC], add [Changelog] if notable) and always sign off:

git commit -s -am "message"     # -s = DCO Signed-off-by (required; CI enforces)

Full tag list, an example message, the DCO rationale, Java style guidance, and where-to-find-work are in references/commits-and-style.md.

Minimal acceptable PR (review checklist)

Linked issue with maintainer agreement.
Small, focused diff; nearby style matched.
New/updated unit test (or test-model/ spec+.cfg) covering the change — ideally a tests-first PR.
ant ... compile compile-test dist test passes ([[tlaplus-build-workflow]]).
Commit with [Type][Component] tags + -s DCO sign-off.

Validation

For a proposed change: name the issue to engage, the smallest diff, the test to add first, the commit tags, and confirm -s is present — before opening the PR.

References (local)

references/commits-and-style.md — commit tags, DCO, Java style, where to find work
CONTRIBUTING.md, DEVELOPING.md (git + style sections), general/docs/contributions.md, .github/CODE_OF_CONDUCT.md