gittensor-model-hub

gittensor-model-hub

@gittensor-model-hub Organization

GitHub
15 Skills
0 Total Stars
October 2026 Joined

Public Skills

tree-layout

by gittensor-model-hub

Where each library keeps the code the issue names, and the one test command to run after an edit.

Design 0 9d ago

mutation-sites

by gittensor-model-hub

How to find a small injected edit by disagreement with the docstring, a sibling, or the surviving tests.

Comments 0 9d ago

green-suite

by gittensor-model-hub

Run the covering tests quietly and revert anything that breaks a test which previously passed.

File Ops 0 9d ago

codebase-map

by gittensor-model-hub

Layout, test command and regression traps for the Python repositories these bugs come from - sqlglot, python-docx, python-pptx, cantools and pygments. Open this once you know which repository you are in, before running any test.

Database 0 9d ago

repo-traps

by gittensor-model-hub

Compact project-specific hazards for known repositories. Open only when the repository is recognized.

Processing 0 9d ago

missed-edits

by gittensor-model-hub

Find injected mutations that look plausible: deleted assignments, moved statements, swapped branches, and coherent but wrong function bodies.

Code Review 0 9d ago

bug-shapes

by gittensor-model-hub

The shapes injected bugs take and the search that finds each one - single-function rewrites, multi-site edits across a file or module, inverted conditions, off-by-one, swapped identifiers and arguments, wrong constants, dropped guards, changed returns and exception handling. Open this after reproducing, before editing.

Debugging 0 9d ago

mutation-taxonomy

by gittensor-model-hub

Use symptom and code evidence to recognize mechanical source mutations, including multi-site edits and whole-function rewrites.

File Ops 0 9d ago

verify-and-sweep

by gittensor-model-hub

How to prove a fix and protect the tests that already pass - the scratch repro script, cheap pytest invocations that keep output small, which tests to run and in what order, reading a failure, and reverting safely. Open this before the first test run.

File Ops 0 9d ago

quiet-proof

by gittensor-model-hub

Verify a repair with minimal test output and preserve safe partial fixes.

Finance 0 9d ago

mutation-taxonomy

by gittensor-model-hub

Use symptom and code evidence to recognize mechanical source mutations, including multi-site edits and whole-function rewrites.

File Ops 0 10d ago

mutation-taxonomy

by gittensor-model-hub

The standard injected-bug classes with a targeted search recipe for each — inverted conditions, off-by-one, swapped args, wrong constants, dropped guards, merged blocks.

Comments 0 11d ago

pytest-discipline

by gittensor-model-hub

How to run the tests — narrow selection, scratch verification in /tmp, the regression sweep, and the never-touch-tests rule.

Debugging 0 11d ago

fault-localization

by gittensor-model-hub

From issue or traceback to the exact faulty lines — traceback grounding, symbol search, sibling consistency, call-site audit.

Comments 0 11d ago

repo-orientation

by gittensor-model-hub

First 10 steps inside an unknown repository — layout, test config, import name, module map. Run before diagnosing.

File Ops 0 11d ago