brainstorming
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).
repo-maintenanceMaintain the torchsummary checkout safely, including package layout, public exports, dependency caveats, focused unittest commands, and safe edit boundaries.
Independent GitHub snapshot · Automated classification · Original documentation governs
Use this sub-skill when the task is to maintain, edit, test, package, or refresh the tiny torchsummary source checkout. It preserves the repository facts needed to make safe changes without reopening external project pages or depending on original checkout paths.
For user-level model summary calls, input_size usage, multiple-input workflows, return values, or interpreting the printed table, route to ../model-summary-usage/SKILL.md instead.
references/testing-and-maintenance.md.references/troubleshooting.md.../../references/repo-provenance.md and ../../references/troubleshooting.md when those root files are present in the generated bundle.torchsummary.1.5.1 from setup.py.torchsummary/__init__.py: summary and summary_string.summary(model, input_size, batch_size=-1, device=torch.device("cuda:0"), dtypes=None)summary_string(model, input_size, batch_size=-1, device=torch.device("cuda:0"), dtypes=None)setup.py declares packages=["torchsummary"] and no install_requires, but runtime source imports both torch and numpy.torch.nn.Module; tests are small and safe, but require working torch and numpy imports.torchinfo project. Preserve that note when editing docs, and prefer migration advice rather than adding broad new features to this legacy package.From the repository root of the checkout being edited:
python - <<'PY'
import inspect
import torchsummary
print(torchsummary.__file__)
print(inspect.signature(torchsummary.summary))
print(inspect.signature(torchsummary.summary_string))
PY
python -m unittest torchsummary.tests.unit_tests.torchsummary_test
If the full unit module fails, run the focused test IDs in references/testing-and-maintenance.md, fix the smallest behavior boundary that explains the failure, then rerun the focused test and the full unit module.
Treat the following as compatibility boundaries unless tests, docs, and generated skill references are updated together:
input_size semantics: tuple means one input; list of tuples means multiple inputs.dtypes order and length expectations.cuda:0 signature and explicit device="cpu" usage on CPU-only hosts.Layer (type), Output Shape, Param #, total/trainable/non-trainable params, and size estimates.