Loading...
Loading...
Found 2,777 Skills
Select an installation method, install NocoBase, and start it locally or on a server. Use when users ask how to install NocoBase, initialize a project, or start a running instance.
Capture idea or task as todo from current conversation context
Archive completed milestone and prepare for next version
Use when encountering bugs, test failures, or error logs that need root cause analysis and fix generation
Automated code review and analysis. Use when: user wants to review code changes, check for issues, analyze complexity, or perform security scans.
This skill should be used when a user wants to decompose an Epic into its complete set of Features all at once, invoked automatically after write-epic completes, or triggered by phrases like "create all features for this epic", "walk me through all the features", "let's break down this epic", or "plan the features for epic
This skill should be used when a developer or QA engineer wants to report a bug, create a bug ticket, document a test failure, log a defect, file an issue found during a QA session, or report something that is broken — for example "report a bug", "create a bug ticket", "I found a defect", "something is broken in task
Use when adding a new project to the user's personal site and resume, or when the user says to make something "live". Covers updating both arjit-me and arjit-resume, compiling the PDF, and pushing.
Find branch coverage gaps in changed code and fix them by writing missing tests. Two analysis layers: Source ↔ Test (logic branches vs test cases) and Spec ↔ Test (requirement scenarios vs test cases, when a spec file is provided). Use when verifying test completeness after implementing a feature or fixing a bug, when auditing whether tests match a spec, or when suspecting untested branches.
Analyzes staged and unstaged files from the full working tree, groups them into functional clusters (test, docs, chore, directory prefix), generates a conventional commit message per group, detects common issues (secrets, debug statements, large files), and executes one commit per group sequentially after presenting a multi-commit plan for confirmation. Falls through to a single-commit flow when all detected files resolve to one group. Trigger: When the user says "commit", "smart commit", or /commit.
Fix a bug with systematic debugging, TDD, and PR workflow
Create a pull request with Conventional Commits formatting, a templated body, and local verification. Use when the user asks to create a PR, open a PR, submit changes for review, or put code up for review.