Modernize

CommunityPopular

t3dotgg

modernize

For getting old prs up to date. Use when asked to rebase a pr or "modernize".

Overview

Publisher	t3dotgg
Repository	`tstack`
Skill name	`modernize`
Stars	2.5K
Forks	153
Bundled files	1
License	MIT
Links	Skill source Repository

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
1 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by t3dotgg on GitHub. Read the source before you install it.

Installation

Install the Modernize AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/t3dotgg/tstack/tree/main/skills/modernize
Enable the skill in any chat where you want it available.

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/t3dotgg/tstack.git /tmp/tstack
mkdir -p .claude/skills
cp -r /tmp/tstack/skills/modernize .claude/skills/modernize

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Modernize in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Modernize on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Modernize is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Modernize

Modernize the idea, not just the branch. A clean rebase does not prove that the PR still belongs in the product.

Guardrails

Always check to make sure you have pulled latest origin for your branch, main branch, and any other branch related to your work before starting.
Treat existing worktree changes as user-owned. Use a disposable worktree when the active worktree is dirty or is being used for other work.
Modernizing authorizes rebasing and updating the PR branch. It does not authorize merging, closing, changing the base branch, or expanding scope.
Never use an unqualified force push. Update a rebased branch with --force-with-lease against the head SHA observed before the rebase.
Do not post a PR comment unless the user asked for one. Use the leaving-pr-comments skill for every comment posted on the user's behalf.

Establish the PR's intent

Resolve the PR and record its URL, state, base, head repository and branch, current head SHA, author, checks, and review state. Read the title, body, linked issues, commits, review threads, and complete diff. State the smallest coherent goal the PR was trying to accomplish before judging its implementation.

Fetch the latest remote base and PR head. Use the PR's actual base branch, usually main, rather than assuming the local branch is current. Record the merge base so the original PR and subsequent base-branch changes can be compared separately.

Check what changed around it

Inspect commits and diffs added to the base branch since the PR diverged. Search merged and open PRs when titles, code paths, or behavior suggest a replacement or competing implementation.

Look beyond overlapping lines:

Has the same user-facing problem already been solved?
Did APIs, types, schemas, dependencies, or architectural boundaries change?
Do both sides now claim ownership of the same behavior or invariant?
Was the code being changed deleted, moved, or intentionally simplified?
Would landing the PR restore an old behavior or create two ways to do the same thing?
Is the original benefit still large enough to justify the maintenance cost?

Do not describe a PR as current merely because Git reports no conflicts.

Choose a disposition before pushing

Use one of these recommendations:

MODERNIZE: the goal is still useful and the implementation remains the right shape. Rebase, resolve conflicts, test, and update the branch.
REWORK: the goal is still useful, but a mechanical rebase would preserve the wrong implementation. Explain the smallest credible rewrite and stop before pushing unless the user also asked for that rework.
CLOSE: the PR is superseded, obsolete, directionally wrong, or no longer worth its cost. Cite concrete evidence and stop. Do not spend time rebasing an obsolete branch, and do not close it without explicit permission.

Be willing to recommend CLOSE. Age alone is not evidence, and sunk effort is not a reason to keep a PR alive.

Rebase without losing intent

For a MODERNIZE disposition:

Create a safe local branch or disposable worktree at the recorded PR head.
Rebase its commits onto the freshly fetched base branch.
Resolve each conflict according to the PR's current intent and the base branch's newer invariants. If a conflict reveals a product or architecture disagreement, stop and reconsider the disposition instead of guessing.
Compare the pre-rebase and post-rebase commit series with git range-diff and inspect the final diff. Confirm that no intentional behavior disappeared and no already-landed behavior was reintroduced.
Run the repository's focused checks for the touched area. Distinguish real failures from pre-existing or infrastructure failures.
Push with --force-with-lease tied to the previously observed remote head. If the lease fails, fetch and reassess rather than overwriting new work.

Do not merge the PR.

Report

Lead with MODERNIZE, REWORK, or CLOSE and the reason. Then summarize:

meaningful changes on the base branch;
conceptual conflicts or confirmation that none were found;
the rebase and push result, if performed;
checks run and their results;
the remaining decision or work, with a link to the PR.

Separate observed facts from judgment. Say what could not be verified instead of manufacturing confidence.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

agents/openai.yaml1 KB

Frequently asked questions

What does the Modernize AI skill do?

For getting old prs up to date. Use when asked to rebase a pr or "modernize".

Why use Modernize on TypingMind?

Because you install it once and use it with any model. Modernize is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Modernize in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/t3dotgg/tstack/tree/main/skills/modernize. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Modernize?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Modernize?

As many as you like. As long as a model supports skills, you can use Modernize with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Modernize AI skill free?

Yes. It is published on GitHub by t3dotgg under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Openclaw Testing

openclaw

OrganizationPopular

Choose proportional OpenClaw tests and checks, diagnose failures, and route environment-sensitive or release proof to its owner.

Release Openclaw Ci

Run, watch, debug, and summarize OpenClaw full release CI, release checks, live provider gates, install/update proofs, and release-secret preflights.

Release Openclaw Mac

Run or recover OpenClaw macOS release signing, notarization, appcast, and asset promotion.

Release Openclaw Maintainer

openclaw

OrganizationPopular

Prepare, publish, recover, or verify OpenClaw beta, stable, and extended-stable releases, including approved backports.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Modernize

Guardrails

Establish the PR's intent

Check what changed around it

Choose a disposition before pushing

Rebase without losing intent

Report

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now