discovering-make-commands
Quickly discover and run Streamlit project maintenance tasks using available make commands.
Install
mkdir -p .claude/skills/discovering-make-commands && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/1446" && unzip -o skill.zip -d .claude/skills/discovering-make-commands && rm skill.zipInstalls to .claude/skills/discovering-make-commands
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Lists available make commands for Streamlit development. Use for build, test, lint, or format tasks.Key capabilities
- →Executes build process for Streamlit frontend
- →Runs automated unit and integration tests
- →Invokes linting and formatting routines for Python/JS
- →Recompiles Protobuf definitions
- →Starts development servers for debugging
How it works
Triggers local shell scripts defined in a project-specific Makefile to maintain repository state.
Inputs & outputs
When to use discovering-make-commands
- →Run python unit tests
- →Format project files
- →Build the frontend
- →Lint protobuf files
About this skill
Available make commands
List of all make commands available for execution from the repository root folder:
help Show all available make commands.
all Install all dependencies, build frontend, and install editable Streamlit.
all-dev Install all dependencies and editable Streamlit, but do not build the frontend.
init Install all dependencies and build protobufs.
clean Remove all generated files.
protobuf Recompile Protobufs for Python and the frontend.
protobuf-lint Lint and check formatting of protobuf files (buf).
protobuf-format Format protobuf files (buf).
python-init Install Python dependencies and Streamlit in editable mode.
python-lint Lint and check formatting of Python files.
python-format Format Python files.
python-tests Run Python unit tests.
python-performance-tests Run Python performance tests.
python-integration-tests Run Python integration tests. Requires `PYTHON_DEPENDENCY_GROUP=integration make python-init` first.
python-types Run the Python type checker.
frontend-init Install all frontend dependencies.
frontend Build the frontend.
frontend-with-profiler Build the frontend with the profiler enabled.
frontend-fast Build the frontend (as fast as possible).
frontend-dev Start the frontend development server.
debug Start Streamlit and Vite dev server for debugging. Use via `make debug my-script.py`.
frontend-lint Lint and check formatting of frontend files.
frontend-types Run the frontend type checker.
frontend-format Format frontend files.
frontend-tests Run frontend unit tests and generate coverage report.
frontend-knip Run Knip with default reporter.
frontend-typesync Check for unsynced frontend types.
update-frontend-typesync Installs missing typescript typings for dependencies.
update-snapshots Update e2e playwright snapshots based on the latest completed CI run.
update-snapshots-changed Update e2e playwright snapshots of changed e2e files based on the latest completed CI run.
update-material-icons Update material icons based on latest Google material symbol version.
update-emojis Update emojis based on latest emoji version.
update-notices Update the notices file (licenses of frontend assets and dependencies).
update-headers Update all license headers.
update-min-deps Update minimum dependency constraints file.
debug-e2e-test Run a playwright e2e test in debug mode. Use it via `make debug-e2e-test st_command_test.py`.
run-e2e-test Run a playwright e2e test. Use it via `make run-e2e-test st_command_test.py`.
trace-e2e-test Run e2e test with tracing and view it. Use via `make trace-e2e-test <test_file.py>::<test_func>`.
lighthouse-tests Run Lighthouse performance tests.
bare-execution-tests Run all e2e tests in bare mode.
cli-smoke-tests Run CLI smoke tests.
check Run all checks (format, lint, types, unit tests) on changed files only. Useful to verify the current state of the codebase before committing.
autofix Autofix linting and formatting errors.
package Create Python wheel files in `dist/`.
When not to use it
- →When working outside of a Streamlit repository
- →For managing non-pythonic dependencies
Prerequisites
Limitations
- →Commands are specific to the Streamlit repo structure
- →Requires specific environment dependencies for success
How it compares
Centralizes complex build and maintenance tasks into standardized, easily discoverable command aliases.
Compared to similar skills
discovering-make-commands side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| discovering-make-commands (this skill) | 3 | 5mo | No flags | Beginner |
| code-change-verification | 4 | 4mo | Review | Beginner |
| dev | 2 | 6mo | Review | Advanced |
| instantly-ci-integration | 1 | 25d | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by streamlit
View all by streamlit →You might also like
code-change-verification
openai
Run the mandatory verification stack when changes affect runtime code, tests, or build/test behavior in the OpenAI Agents Python repository.
dev
atopile
LLM-focused workflow for working in this repo: compile Zig, run the orchestrated test runner, consume test-report.json/html artifacts, and discover/debug ConfigFlags.
instantly-ci-integration
jeremylongshore
Configure Instantly CI/CD integration with GitHub Actions and testing. Use when setting up automated testing, configuring CI pipelines, or integrating Instantly tests into your build process. Trigger with phrases like "instantly CI", "instantly GitHub Actions", "instantly automated tests", "CI instantly".
generate-validation-notebook
monte-carlo-data
Generate SQL validation notebooks for dbt changes. Pass a GitHub PR URL or local dbt repo path.
testing
hw-native-sys
Testing guide and pre-commit testing strategy for PTO Runtime. Use when running tests, adding tests, or deciding what to test before committing.
release-bump
himatts
Prepare versioned release updates for Lime Pipeline. Use when user-visible behavior changes require bumping `bl_info["version"]`, updating `CHANGELOG.md`, and producing release-ready QA notes.