Loading...
Loading...
Found 1,433 Skills
Use when analyzing PR review comments to determine relevance, identify ambiguities, and generate a comprehensive report without making code changes. Useful for understanding feedback landscape and initiating collaborative Q&A discussions about unclear or potentially outdated comments.
Use when needing to check PR review comments on current branch, before addressing reviewer feedback, or when asked to fetch/review PR comments
Take a list of projects and their related documentation, and organize them into the SRED format for submission.
Create high-quality Pull Requests with conventional commits and proper descriptions. Trigger: When creating PRs, writing PR descriptions, or using gh CLI for pull requests.
Respond to PR review feedback with maximum transparency. Analyze feedback, get second opinions on non-trivial decisions, post comments documenting every judgment, and implement fixes. All reasoning must be visible in PR comments. Keywords: PR review, code review response, review feedback, address comments, fix review.
Create documentation-first PRDs that guide development through user-facing content
CI/CD Pipelines, Versioning & Release Management
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 pr-manager - invoke with $agent-pr-manager
Multi-repository coordination, synchronization, and architecture management with AI swarm orchestration
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.