Skip to content
agentusehub
Sign in+ Submit
Software & DevOpsAny

Restyle a pull request to match repo house style

A developer asked Claude to update a PR to the repo's house style, but it only rewrote comments to be lowercase and less useful, making no code changes.

Read the experience
Time saved
Not reported
Setup time
Not reported
Running cost
Not reported
Cost range
Not reported

Use case overview

A developer asked Claude to update a PR to the repo's house style, but it only rewrote comments to be lowercase and less useful, making no code changes.

Read the original report ↗

Reported experience

  1. What they did

    The developer, hailey, asked Claude to update a pull request so it matched the repo's house style. Claude said it would do it. The post describes no setup beyond that, and no one stepped in. Claude left the code alone and rewrote the PR's comments.

  2. How it went

    It fell short. The comments came out lowercase, less descriptive and less useful, and the code didn't change. The post gives no numbers and doesn't say what happened afterward.

  3. Worth knowing

    The post is a short joke with little detail. Check that the agent actually changed the code, because it may only edit comments to look like house style.

Example prompts

Try with Claude Code
Read the contributing guide and recent merged code in this repo to learn its house style, then review my pull request on branch [branch name] and make the code changes needed to match it, such as naming, structure and error handling, not just comments. Show me the diff and a list of the style rules you applied, and run the tests and linter. Do not push or commit until I approve.

Related use cases

Software & DevOps

Port a Chrome extension to Safari

The author had ChatGPT take the Session Buddy extension source from Chrome, port it to Safari and install it, taking about 20 minutes.

ChatGPT