11 skills (repositories by breaking-brake) · sorted by popularity
Advance one development task by managing an existing pull request, fixing a build failure or bug, or implementing a queued idea. Record the work and integrate changes into auto-dev only after automated checks pass.
Prepare a pull request to main in the specified pnpm monorepo, where multiple packages share one repository. Identify affected packages, ensure Changesets release records are appropriate, run checks and builds, and write an English review submission.
Use ccwf to validate workflow JSON files, preview their steps in a browser, and produce Mermaid flowcharts. Export workflows as skill files for supported agents, or generate the files and launch Claude Code to proceed with execution.
Adjust how AI agents generate workflows in cc-wf-studio by reviewing node descriptions, examples, and misleading constraints. The skill guides minimal schema edits, format regeneration, and testing to address biased node choices.
Find a valuable gap in test coverage by checking code, existing tests, and QA priorities. The skill creates at most one locked GitHub issue with concrete test cases, ready for later implementation.
Turn previously retrieved Jira requirements and Confluence documents into a structured implementation plan. Tasks are grouped into frontend, backend, and infrastructure work, with architectural reasoning, blocking dependencies, and risks paired with mitigation measures.
Advance one queued QA task by adding tests or test tooling, recording the work, and opening a pull request. The skill also manages its in-flight QA requests and merges into auto-qa after CI passes.
Check GitHub pull request review comments against the actual code. Classify findings as valid, invalid, or partially valid, identify similar issues elsewhere, and produce recommended actions, with optional replies after user approval.
Create and edit visual AI agent workflows in CC Workflow Studio through conversation. Add or remove steps and connections, update individual nodes, and organize related steps into visual groups on the canvas.
Clean up a feature branch after its pull request is merged into main. Switch to main, pull the latest changes, and delete both local and remote branches, including branches merged through a squash merge.
Develop user-visible improvements for cc-wf-studio, verify their basis in the code, and assess their value. Record qualifying proposals as locked GitHub issues, creating a queue of concrete ideas for later implementation without changing code.