Add known issues with titles, descriptions, categories, and severity to project memory.
npx skills add https://github.com/GDSDN/kord-aios --skill gotcha
Please help me install this Agent Skill. Skill: gotcha Source: https://github.com/GDSDN/kord-aios/tree/main/src/features/builtin-skills/kord-aios/documentation/gotcha Command: npx skills add https://github.com/GDSDN/kord-aios --skill gotcha
This Skill helps developers and teams document and manage known issues, workarounds, and potential pitfalls within a project, preventing recurring mistakes and improving knowledge sharing.
gotcha skill to record the problem, the workaround, and mark it as a 'build' category 'critical' severity, ensuring future team members can quickly find and apply the solution.Add a new gotcha to the project's memory by providing its title and an optional description.
High-intent search queries and answers about installing and using this skill.
You can document known issues by manually adding a gotcha to the project's memory, storing the title, description, category, and severity to prevent recurring mistakes. This approach ensures team members can quickly find and apply the correct workaround.
Automated categorization for project gotchas works by intelligently suggesting categories like build, test, lint, or runtime based on keywords found in the gotcha's title and description. This allows for quick classification without manual sorting.
The best way to track build configuration issues is to record the problem and workaround as a gotcha, marking it with a 'build' category and 'critical' severity. This ensures future team members can quickly find and apply the solution.
Yes, you can manually override the severity and related files for a known issue. While the system supports automated category detection based on keywords, it allows manual overrides to ensure accurate tracking of specific project pitfalls.
Documented project gotchas are stored for persistent retrieval by integrating with GotchasMemory. This integration ensures that recorded issues, workarounds, and potential pitfalls remain accessible for future reference across the project lifecycle.
You should document a workaround as a gotcha when you need to record known issues, build configurations, or potential pitfalls that cannot be immediately resolved. This prevents recurring mistakes by ensuring the team has immediate access to the temporary solution.
desibarraConfigure Supabase PostgreSQL authentication and memory storage for SaaS apps.
GDSDNManage and retrieve project issues with categories, severities, and workarounds.
lpjhelderAutomates QA cycling to detect, diagnose and fix failing builds, lint, typecheck, and tests.
EvolutionAPIDraft publish-ready knowledge base articles from resolved issues or FAQs.