Skip to content

gpsaggese/helpers / .claude/skills/skill.reorganize_rules

skill.reorganize_rules

Verified

Reorganize the rules in a skill rules file

Goal

  • Given a rule file <RULE_FILE> in the format <TOPIC>.rules.md passed by the user, propose and apply a better organization of its sections

Workflow

Read the Rule File

  • Read <RULE_FILE> content

Read Skill Rules

  • Read .claude/skills/skill.rules.md

Propose the Reorganization

  • Propose changes to the user if you see:
    • A better organization of H1 sections that is more cohesive and simpler
    • An H2 section or text that is redundant
    • An H2 section that belongs under a different H1 section for better cohesion
  • Do not change the content or intention of <RULE_FILE>

Present the New Organization

  • Print the new organization in terms of H1 and H2 headers
  • Ask the user to confirm

Save the Result

  • Save the result in the same file <RULE_FILE>

Update References

  • Look for all the files referring to <RULE_FILE> and update them to refer to the updated structure of <RULE_FILE>
    • E.g., update chunks of code like
      - Add end-to-end tests for command-line tools using the rules in
        `.claude/skills/testing.rules.md`
          `# End-to-end Unit Tests for Executables`
      
      to match the new organization

Verification

  • The user confirmed the new organization before <RULE_FILE> was saved
  • The content and intention of <RULE_FILE> are unchanged
  • Every file referencing <RULE_FILE>'s old structure was updated
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: 468kUpdated 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: 321kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 321kUpdated 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: 321kUpdated Claude CodeCodexVerifiedInstall