skills.rest
NaoyaMiyagawa
NaoyaMiyagawaCOMMUNITY
Explore all skills by this author →
𝕏@_miya_nm7GitHub

daily-small-refactoring-based-on-github-issue

Creates small refactoring pull requests from assigned GitHub issues with CI fixes.

1|Updated Apr 3, 2021
Search Tags:#automation#git#code review#pull request#refactoring#github issues#ci
One-click install
npx skills add https://github.com/NaoyaMiyagawa/dotfiles --skill daily-small-refactoring-based-on-github-issue-naoyamiyagawa
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: daily-small-refactoring-based-on-github-issue
Source: https://github.com/NaoyaMiyagawa/dotfiles/tree/main/.claude/scheduled-tasks/daily-small-refactoring-based-on-github-issue
Command: npx skills add https://github.com/NaoyaMiyagawa/dotfiles --skill daily-small-refactoring-based-on-github-issue-naoyamiyagawa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It automates the routine of turning self-assigned GitHub issues into small, reviewable refactoring pull requests, keeping code quality work moving without large context switches. ## Core Features & Use Cases - Issue-Driven Refactoring: Picks up GitHub issues assigned to the user and raises a PR when no linked PR already exists. - Small, Reviewable Changes: Keeps code changes under roughly 200 lines and limits output to at most 2 PRs per run. - Structured Review Loop: Performs self-review, cross-review with a different AI model (Codex), and fixes CI failures until linter and tests pass. - Use Case: Run it daily to chip away at a backlog of refactoring issues, recording progress as a checklist on the issue when one PR cannot resolve it fully. ## Quick Start Ask the assistant to look at my assigned GitHub issues and raise a small refactoring PR based on origin/develop.

Frequently Asked Questions about daily-small-refactoring-based-on-github-issue

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate refactoring PRs from GitHub issues?▼

This routine reads issues assigned to the user, checks for an existing linked PR, and creates a new branch from origin/develop to raise a small refactoring PR. Progress is tracked as a checklist on the issue when the work spans multiple rounds.

How large can the refactoring pull requests be?▼

Code changes should preferably be fewer than 200 lines in total so reviewers can evaluate them quickly. If one PR cannot resolve the issue, the remaining work is recorded as a checklist on the issue for the next run.

How many PRs does this routine create per run?▼

It creates at most 2 PRs per run and skips creating new ones if there are already 2 or more open refactoring PRs from this routine. This keeps the PR list manageable for reviewers.

What happens when CI fails on the refactoring PR?▼

The routine fixes CI errors until the linter and tests pass. It follows a review flow of self-review, fix and push, cross-review with a different AI model (Codex), then fix and push again.

Which branch are refactoring PRs based on?▼

Branches are created after running git fetch --all and are based on origin/develop. This ensures the refactoring work starts from the latest shared development branch.

Related Skills

Explore More Software Engineering Skills→
intraleintrale

priorizar

Triage unlabelled GitHub issues and assign labels and project backlogs.

Official
Advanced
devbasexdevbasex
1

merged

Delete merged branches and worktrees with approval, then update the base branch.

Official
Advanced
wowsignal-iowowsignal-io
26

presubmit

Run presubmit checks to validate code readiness before merging.

Official
Advanced
carl10086carl10086
7

incremental-implementation

Implement complex software features through small, verifiable code increments.

Community
Intermediate