Skip to main content
Run any Skill in Manus
with one click
GitHub repository

sigit

sigit contains 7 collected skills from getsigit, with repository-level occupation coverage and site-owned skill detail pages.

skills collected
7
Stars
23
updated
2026-07-06
Forks
1
Occupation coverage
1 occupation categories · 100% classified
repository explorer

Skills in this repository

run-sigit
software-developers

Build, launch, and drive the sigit AI coding agent — run the ACP server, screenshot the interactive TUI, smoke-test the CLI. Use when asked to run sigit, start the agent, screenshot the chat UI, or verify a change to the binary.

2026-07-06
commit-message
software-developers

Write a clear git commit message from staged changes. Use when the user asks to commit, write a commit message, or describe staged changes.

2026-06-29
sigit-code-release
software-developers

Prepare and verify siGit Code releases. Use when bumping versions, checking Cargo, npm, or PyPI package metadata, validating release notes, confirming CI readiness, or assembling a release checklist for a new siGit Code version.

2026-06-28
agent-client-protocol
software-developers

Implement or debug Agent Client Protocol (ACP) support in Rust for siGit Code. Use when working on ACP JSON-RPC over stdio, the agent-client-protocol crate, session/prompt/fork handlers, config options (model picker), slash commands, streaming notifications, or editor integration.

2026-06-24
ai-assisted-coding
software-developers

Build or maintain AI-assisted coding features in Rust using Onde Inference. Use when working on ChatEngine integration, model loading, streaming inference, history management, sampling config, or local coding-agent architecture.

2026-06-24
tool-calling
software-developers

Implement or debug tool calling in siGit Code across the app, Onde Inference, and mistral.rs. Use when working on tool schemas, execution loops, model support, session cwd handling, or tool-call troubleshooting.

2026-06-24
branding
software-developers

Keep siGit Code branding, naming, and package references consistent. Use when editing docs, release notes, UI copy, package metadata, setup guides, or any prose that mentions the product, CLI, company, or Onde Inference.

2026-05-29