Kilo
🥈SilverKilo is an AI assistant that automates repetitive tasks for engineers. It integrates with coding agents like Claude Code and Cursor to boost productivity. Engineers use it to speed up code reviews, debugging, and documentation. It connects to development workflows to reduce manual effort.
15926472installsUpdated 2mo ago
Beginner15 minutes to implementdevelopment
Saves ~30 min per use
Quick InstallView Source
npx skills add sh/agentsWorks with:
Claude CodeCursorWindsurfClineCodex
Overview
About This Skill
Kilo is an AI assistant that automates repetitive tasks for engineers. It integrates with coding agents like Claude Code and Cursor to boost productivity. Engineers use it to speed up code reviews, debugging, and documentation. It connects to development workflows to reduce manual effort.
How to Use
1. **Set Up Integration:** Ensure Kilo is connected to your repository (GitHub/GitLab) and has access to your coding agent (Claude Code/Cursor). Configure the API keys for your version control system. 2. **Trigger Review:** Paste the prompt template into your AI assistant, replacing [REPOSITORY_PATH] with your project path (e.g., `~/projects/acme-corp/backend`), [PULL_REQUEST_NUMBER] with your PR number (e.g., 42), and [LANGUAGE] with your primary language (e.g., 'simple English'). 3. **Execute Review:** Run the command in your terminal or AI assistant interface. Kilo will analyze the code changes and generate a comprehensive review. 4. **Review Output:** Examine the issues identified, suggested fixes, and test cases. Prioritize critical issues (security, performance) over minor style suggestions. 5. **Implement Feedback:** Apply the suggested fixes to your codebase. Use the unit test suggestions to expand your test coverage. Commit the changes with messages referencing Kilo's suggestions (e.g., 'Fix hardcoded API key - Kilo #42'). **Pro Tips:** - For large PRs (>500 lines), ask Kilo to review in batches using file paths - Customize the coding style by providing a `.clang-format` or `.prettierrc` file to Kilo - Use Kilo's documentation generation feature to update your README files automatically
Use Cases
Task automation
Data analysis
Scheduling assistance
Best For
Developers
Tags
Setup & Installation
Quick Install
Terminal
npx skills add sh/agentsAlternative Install (Git Clone)
git clone https://github.com/sh/agentsRequirements
- Claude Code or compatible AI agent
- Works with: Claude Code, Cursor, Windsurf, Cline, Codex
Quick Start Guide
1
Install the Skill
Copy the install command above and run it in your terminal.
2
Open Your AI Agent
Launch Claude Code, Cursor, or your preferred AI coding agent.
3
Try It Out
Use the prompt template or examples below to test the skill.
4
Customize
Adapt the skill to your specific use case and workflow.
Usage Examples
Prompt Template
Act as Kilo, an AI engineering assistant. Review the code changes in [REPOSITORY_PATH] for [PULL_REQUEST_NUMBER]. Identify at least 3 potential issues: 1) [TYPE_OF_ISSUE], 2) [TYPE_OF_ISSUE], and 3) [TYPE_OF_ISSUE]. For each issue, provide: a) the exact line number, b) a concise explanation of the problem, c) a suggested fix, and d) the impact if left unresolved. Also generate a summary of the changes in [LANGUAGE] that a non-technical stakeholder would understand. Finally, suggest 2-3 unit tests that should be added to cover the new functionality. Use the coding style of the repository.
Example Output
### Code Review for PR #42 in `acme-corp/backend`
**Summary for Stakeholders:**
This pull request implements a new `PaymentGateway` service that integrates with Stripe for our subscription billing system. The changes include:
- Added a new `stripe_client.py` module to handle API interactions
- Modified the `SubscriptionService` to use the new gateway
- Updated the `billing_cycle.py` to support monthly/yearly billing options
- Added comprehensive logging for all payment operations
**Key Issues Identified:**
1. **Line 47 - stripe_client.py**
- **Issue:** The `api_key` is hardcoded in the client initialization
- **Explanation:** This violates security best practices by exposing credentials in the codebase
- **Suggested Fix:** Use environment variables with `os.getenv('STRIPE_API_KEY')`
- **Impact:** Potential security vulnerability if code is committed to public repositories
2. **Line 112 - subscription_service.py**
- **Issue:** Missing error handling for failed Stripe API calls
- **Explanation:** The code assumes all API calls succeed without retry logic
- **Suggested Fix:** Wrap Stripe calls in try-catch blocks with exponential backoff
- **Impact:** System crashes during payment processing if Stripe experiences downtime
3. **Line 203 - billing_cycle.py**
- **Issue:** No validation for negative billing amounts
- **Explanation:** The code allows negative values which could lead to refunds
- **Suggested Fix:** Add validation: `if amount <= 0: raise ValueError('Amount must be positive')`
- **Impact:** Potential financial losses from incorrect billing amounts
**Suggested Unit Tests:**
1. Test `stripe_client.py` with invalid API keys to verify proper error handling
2. Test `subscription_service.py` for retry behavior during Stripe API failures
3. Test `billing_cycle.py` with edge cases (zero amount, very large amounts)
**Additional Recommendations:**
- Consider adding integration tests with a mock Stripe server
- Add documentation for the new billing options in the README
- Update the deployment checklist to include Stripe API key configurationApply to these tools
Browse all tools
Compatible MCP servers
Browse all MCP servers
Find the right skills for your stack
Take a free 3-minute scan and get personalized AI skill recommendations.
Take free scan