Safely push ToolUniverse code to GitHub by enforcing pre-push cleanup, pre-commit hooks, and test validation.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versiondevtu-githubExecute the skills CLI command in your project's root directory to begin installation:
Fetches devtu-github from mims-harvard/tooluniverse and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate devtu-github. Access via /devtu-github in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
1.2K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
1.2K
stars
Safely push ToolUniverse code to GitHub by enforcing pre-push cleanup, pre-commit hooks, and test validation.
When the user wants to push code, fix CI, or prepare a commit, follow this workflow:
# Move session markdown files to temp_docs_and_tests/
for f in $(ls *.md 2>/dev/null | grep -v README.md | grep -v CHANGELOG.md | grep -v LICENSE.md); do
mv "$f" temp_docs_and_tests/
done
# Move root-level test scripts to temp_docs_and_tests/
for f in $(ls test_*.py 2>/dev/null); do
mv "$f" temp_docs_and_tests/
done
git status --short
Red flags - these should NEVER be staged:
*_SUMMARY.md, *_REPORT.md, SESSION_*.md in roottest_*.py in root (these are ad-hoc scripts, not real tests).env or credential filestemp_docs_and_tests/ contentspre-commit install
This enables automatic checks on every git commit:
ruff check --fix - Python linting with auto-fixruff format - Code formattingls -la .git/hooks/pre-commit
python -m pytest tests/ -x --tb=short -q
git add . or git add -A):git add src/tooluniverse/specific_file.py tests/specific_test.py
git commit -m "Clear, descriptive message"
git fetch origin
git stash # stash any uncommitted work
git rebase origin/main
git stash pop # restore uncommitted work
If rebase conflicts arise, resolve them (keep our newer changes), then:
git add <conflicted-file>
git rebase --continue
git push --force-with-lease origin <branch-name>
After pushing, verify the PR is conflict-free:
gh pr view <PR-number> --json mergeable,mergeStateStatus
# Must show: "mergeable":"MERGEABLE"
These are session notes created during development. Move to temp_docs_and_tests/ before committing:
| Pattern | Example |
|---|---|
*_SUMMARY.md |
API_DISCOVERY_SESSION_SUMMARY.md |
*_REPORT.md |
SKILL_TESTING_REPORT.md, TOOLUNIVERSE_BUG_REPORT.md |
SESSION_*.md |
SESSION_2026_02_13.md |
IMPLEMENTATION_*.md |
IMPLEMENTATION_COMPLETE.md |
BUG_ANALYSIS_*.md |
BUG_ANALYSIS_DETAILED.md |
FIX_*.md |
FIX_SUMMARY.md, CORRECT_FIX.md |
AGENT_*.md |
AGENT_DESIGN_UPDATES.md |
Exception: README.md, CHANGELOG.md, LICENSE.md are real docs and MUST stay.
Ad-hoc test scripts like test_*.py in root are NOT part of the test suite (tests/ directory is). Move them to temp_docs_and_tests/:
| File | Purpose |
|---|---|
test_clear_tools.py |
One-off tool cleanup test |
test_finemapping_tools.py |
Ad-hoc tool validation |
test_metabolomics_tools.py |
Ad-hoc tool validation |
test_original_bug.py |
Bug reproduction |
test_pathway_tools.py |
Ad-hoc tool validation |
test_protein_interaction_skill.py |
Skill test |
test_reload_fix.py |
Bug reproduction |
test_round10_tools.py |
Ad-hoc tool validation |
.env - Environment variables with secretstemp_docs_and_tests/ - Already in .gitignore.claude/ - Claude Code configuration__pycache__/, *.pyc - Python bytecode.DS_Store - macOS metadataSymptom: KeyError: 'role' when accessing message dicts
Fix: Add return_message=True to tu.run() and use .get():
messages = tu.run(calls, use_cache=True, return_message=True)
if msg.get("role") == "tool":
Symptom: TypeError: 'Mock' object is not subscriptable
Fix: Use real dicts for all_tool_dict and add _get_tool_instance:
mock_tu.all_tool_dict = {"Tool": mock_tool}
mock_tu._get_tool_instance = lambda name, cache=True: mock_tu.all_tool_dict.get(name)
Fix F841 (unused variable): Use _ prefix or _ = func()
Fix E731 (lambda assignment): Replace with def
Symptom: git status shows temp files as modified/staged
Fix:
git rm -r --cached temp_docs_and_tests/
git rm --cached API_DISCOVERY_SESSION_SUMMARY.md
git commit -m "Remove temp files from tracking"
The project uses .pre-commit-config.yaml:
repos:
- repo: https://github.com/pre-commit/pre-commit-hooks
hooks: [end-of-file-fixer, trailing-whitespace, check-yaml, check-toml]
- repo: https://github.com/astral-sh/ruff-pre-commit
hooks: [ruff-check --fix, ruff-format]
Scope: Only files matching ^(ToolUniverse/)?src/tooluniverse/
| Task | Command |
|---|---|
| Activate hooks | pre-commit install |
| Run all tests | pytest tests/ -x --tb=short -q |
| Run specific test | pytest tests/path/test.py::Class::method -xvs |
| Check staged files | git status --short |
| Unstage a file | git restore --staged <file> |
| Remove from tracking | git rm --cached <file> |
| Move temp files | See Phase 1 commands |
| Run hooks manually | pre-commit run --all-files |
Before every push, verify:
temp_docs_and_tests/test_*.py scripts moved to temp_docs_and_tests/pre-commit install)pytest tests/ -x).env, no temp files)git add <specific-files> instead of git add .Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
mattpocock/skills
devtu-github fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
devtu-github has been reliable in day-to-day use. Documentation quality is above average for community skills.
I recommend devtu-github for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Solid pick for teams standardizing on skills: devtu-github is focused, and the summary matches what you get after install.
I recommend devtu-github for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Solid pick for teams standardizing on skills: devtu-github is focused, and the summary matches what you get after install.
devtu-github reduced setup friction for our internal harness; good balance of opinion and flexibility.
devtu-github is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Keeps context tight: devtu-github is the kind of skill you can hand to a new teammate without a long onboarding doc.
Useful defaults in devtu-github — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
showing 1-10 of 28