Skip to content

gpsaggese/helpers / .claude/skills/skill.auto_add

skill.auto_add

Verified

Update a skill or prompt using lessons learned from a file's Git history

FileKindSize
SKILL.mdskill md3.1 KB
---
description: Update a skill or prompt using lessons learned from a file's Git history
argument-hint: <FILE> <PROMPT>
model: sonnet
---

# Goal

- The user gives two arguments:
  - `<FILE>`: a path to a file edited across one or more Git commits
  - `<PROMPT>`: a path to a skill (`SKILL.md`) or prompt file to improve
- The edits to `<FILE>` encode a lesson: someone fixed by hand what `<PROMPT>`
  should have gotten right the first time
- Update `<PROMPT>` so that, given the original `<FILE>`, it would produce the
  final `<FILE>`
- Generalize: infer the underlying *rule*. Do not hard-code the strings from this
  one diff

# Inputs

- If `<FILE>` or `<PROMPT>` is missing or ambiguous, stop and ask the user. Do not
  guess
- If `<FILE>` has no committed changes, report that and stop

# Workflow

## Determine the Changes

- Find the commits that touched `<FILE>`:
  ```bash
  > git log --oneline --follow -- <FILE>
  ```
- Identify the *first* and *last* relevant revisions. Default to the full history.
  If the user named a range, use that instead
- Extract `<CHANGES>` as a unified diff:
  ```bash
  > git diff <FIRST_SHA> <LAST_SHA> -- <FILE>
  ```
  - If the diff is large, also read the final version to see the intended end
    state, not just the deltas:
    ```bash
    > git show <LAST_SHA>:<FILE>
    ```
- Do not use interactive commands (e.g., `git difftool`). They block

## Read the Prompt and the Conventions

- Read `<PROMPT>` in full
- Read `.claude/skills/skill.rules.md` for the rules that govern how skills and
  prompts are written
- Read any files `<PROMPT>` references, so you do not duplicate a rule that
  already lives elsewhere

## Infer the Rules

- For each meaningful hunk in `<CHANGES>`, note:
  - What changed (before -> after)
  - The general rule it implies
  - Whether `<PROMPT>` already covers it (fully, partially, not at all)
- Drop hunks that are one-off content edits, not repeatable rules (e.g., a typo
  fix, a date update). Say which hunks you dropped and why
- Merge restated rules. Prefer one sharp rule over three overlapping ones

## Improve the Prompt

- Draft the minimal edit to `<PROMPT>` that encodes the inferred rules:
  - Amend an existing rule when one is close but imprecise
  - Add a new rule only when no existing rule covers the case
  - Keep the structure, heading style, and voice of `<PROMPT>`
  - State rules as imperatives, with a short before/after example when a rule is
    easy to misread
- Do not grow the prompt unnecessarily. If the new rule makes an old one
  redundant, remove the old one

## Apply via rules.add

- Follow `.claude/skills/rules.add/SKILL.md`: propose the change to the user
  first, then apply it once approved

# Output

Report, in this order:

1. The commit range and files inspected
2. A table of inferred rules: change observed -> rule -> covered / new
3. The proposed diff to `<PROMPT>`
4. Anything you deliberately did not encode, and why

# Verification
- [ ] The proposed diff was shown to the user before `<PROMPT>` was changed
- [ ] Each inferred rule is a general rule, not a hard-coded string from the one
      diff inspected
- [ ] No rule made redundant by the new edit was left in `<PROMPT>`
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall