Search
Jira · Refactoring
Skills
Sort:BestMost starsTrending todayTrending this weekTrending this monthNewestRecently updatedName
| # | Skill | Repository | Stars | Used in | Tokens | Auto-check | Licence | Updated |
|---|---|---|---|---|---|---|---|---|
| 1 | Nightly refactor review: find the systems the last day's commits hit hardest, use three weeks of history to tell fragile from fast-moving, write a plan per systemic fix, and file deduplicated Jira… | BuilderIO/ | 7.1k | — | ~957 | Automated safety check: Pass | No licence | today |
| 2 | File and track refactor findings in Jira without duplicates: match a run against existing refactor-findings tickets, create tickets from plan files (Pod, label, attached plan, run link), record… | BuilderIO/ | 7.1k | — | ~779 | Automated safety check: Pass | No licence | today |
| 3 | Given a bug report (GitHub issue, Jira ticket, file, or pasted text), find its root cause and decide per symptom whether it is a one-off or one instance of a pattern worth fixing at the root, then… | BuilderIO/ | 7.1k | — | ~1k | Automated safety check: Pass | No licence | today |
| 4 | Judge whether a system is fragile or just fast-moving, and write a ticket-ready refactor plan for one root problem, with measured evidence and a stable fingerprint. | BuilderIO/ | 7.1k | — | ~379 | Automated safety check: Pass | No licence | yesterday |
| 5 | Shared library and file contracts for the fragility skills (system-history, bug-trace, refactor-plan, jira-refactor-findings, identify-fragile-systems, investigate-bug). | BuilderIO/ | 7.1k | — | ~618 | Automated safety check: Pass | No licence | yesterday |
