ReddRadar
Topic: acp
48 skills in this topic.
-
pr-fix
PR Review Fix: automatically fix all issues identified in a pr-review report.
Use when: (1) User says "fix all review issues", (2) User says "/pr-fix",
(3) After pr-review skill has produced a report, (4) User wants to address PR review feedback.
iOfficeAI/AionUi 21,588
-
architecture
Project architecture and file structure conventions for all process types.
Use when: (1) Creating new files or modules, (2) Deciding where code should go,
(3) Converting single-file components to directories, (4) Reviewing code for structure compliance,
(5) Adding new bridges, services, agents, or workers.
iOfficeAI/AionUi 21,588
-
bump-version
iOfficeAI/AionUi 21,588
-
fix-issues
Auto-fix GitHub issues labeled as bugs: fetch open bug issues, analyze feasibility,
fix code, and submit PRs. One issue per invocation.
Use when: (1) User says "/fix-issues", (2) User asks to fix GitHub issues.
iOfficeAI/AionUi 21,588
-
fix-sentry
Auto-fix high-frequency Sentry issues: fetch issues > N occurrences, analyze stack traces,
fix code, create GitHub issues, and submit PRs.
Use when: (1) User says "/fix-sentry", (2) User asks to fix Sentry issues.
iOfficeAI/AionUi 21,588
-
i18n
Internationalization (i18n) workflow and standards for managing translations.
Use when: (1) Adding new user-facing text, (2) Creating new components with user-facing text,
(3) Reviewing code for i18n compliance, (4) Adding a new translation module.
iOfficeAI/AionUi 21,588
-
oss-pr
Use when creating a pull request, after committing changes, or when user invokes /oss-pr. Covers branch management, quality checks, commit, push, and PR creation.
iOfficeAI/AionUi 21,588
-
pr-automation
PR Automation Orchestrator: poll open PRs, check CI, run review, fix, and merge eligible PRs.
Use when: (1) Invoked by daemon via scripts/pr-automation.sh, (2) User says "/pr-automation".
iOfficeAI/AionUi 21,588
-
writing-skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment
xintaofei/codeg 674
-
dispatching-parallel-agents
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
xintaofei/codeg 674
-
using-git-worktrees
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification
xintaofei/codeg 674
-
finishing-a-development-branch
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
xintaofei/codeg 674
-
receiving-code-review
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
xintaofei/codeg 674
-
using-superpowers
Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
xintaofei/codeg 674
-
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
xintaofei/codeg 674
-
executing-plans
Use when you have a written implementation plan to execute in a separate session with review checkpoints
xintaofei/codeg 674
-
requesting-code-review
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
xintaofei/codeg 674
-
subagent-driven-development
Use when executing implementation plans with independent tasks in the current session
xintaofei/codeg 674
-
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
xintaofei/codeg 674
-
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code
xintaofei/codeg 674
-
verification-before-completion
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
xintaofei/codeg 674
-
writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code
xintaofei/codeg 674
-
pr-writing-review
Extract and analyze writing improvements from GitHub PR review comments. Use when asked to show review feedback, style changes, or editorial improvements from a GitHub pull request URL. Handles both explicit suggestions and plain text feedback. Produces structured output comparing original phrasing with reviewer suggestions to help refine future writing.
evalstate/fast-agent 3,743
-
session-investigator
Investigate fast-agent session and history files to diagnose issues. Use when a session ended unexpectedly, when debugging tool loops, when correlating sub-agent traces with main sessions, or when analyzing conversation flow and timing. Covers session.json metadata, history JSON format, message structure, tool call/result correlation, and common failure patterns.
evalstate/fast-agent 3,743