Loading...
Loading...
Found 1,511 Skills
Automated commit analysis and regression detection for AItrader. 自动化提交分析和回归检测。 Use this skill when: - Running regression checks after code changes (代码修改后运行回归检测) - Analyzing git commit history (分析 git 提交历史) - Using AI to analyze code changes (使用 AI 分析代码变更) - Checking if fix commits are still correctly applied (检查修复是否正确应用) - Before merging PRs (合并 PR 前) Keywords: commit, regression, analysis, git, fix, validation, AI, 提交, 回归, 分析
Amp Team Usage
Complete PRD implementation workflow - create branch, push changes, create PR, merge, and close issue
Pull latest groove skills and apply pending migrations to local groove state.
Issue creation expertise and convention enforcement. Auto-invokes when creating issues, writing issue descriptions, asking about issue best practices, or needing help with issue titles. Validates naming conventions, suggests labels, and ensures proper metadata.
Reproduce and investigate a bug using logs, console inspection, and browser screenshots
Plan a new feature from concept to approved implementation plan. Activates Product Council for strategic evaluation, then Feature Council for technical planning. Produces a documented decision and scoped task breakdown. Use when starting any new feature work.
Audit PostHog survey SDK features and version requirements
Agent skill for swarm-issue - invoke with $agent-swarm-issue
Automatically create a PR to register insights, conventions, and best practices obtained from the current project as rules in the TBSten/skills repository. It runs the entire end-to-end process: collecting insights from the project's CLAUDE.md, .claude/rules/ directory and codebase, packaging them as reusable Claude Code rules, and creating the PR. Rules are files stored in .claude/rules/, and unlike skills, they do not require frontmatter. RULE.md serves as the main rule body, while detailed documentation (<rule-name>.md / <rule-name>.ja.md) is placed directly under the rules/ directory. Use when the user requests: "Register insights as rules", "contribute rule", "Share this rule", "Register as a rule", "Compile rules into a PR", "Turn this convention into a rule", "Turn best practices into rules". gh CLI and git must be installed.
Primary pipeline review step after verified implementation. Use to create a PR with lineage and run architectural review before merge. Not for QA intake, planning, or implementation work.
This skill should be used when a designer is picking up a Task issue to add design coverage. Triggers on phrases like "I want to design task