Skip to content

arminzou/dotbrain / plugin/skills/repo-rules

repo-rules

Verified

Initializes and reconciles repository requirements in RULES.md and agent routing in AGENTS.md, and assesses enforcement gaps. Use when asked to establish repository rules, maintain adopted requirements, or assess or hand off their enforcement.

FileKindSize
SKILL.mdskill md7.1 KB
agents/openai.yamlconfig118 B
references/rules-maintenance.mdmarkdown3.3 KB

references/rules-maintenance.md

View on GitHub
# Rules maintenance

These examples show how common engineering requirements can be expressed and
maintained once a repository has adopted them. They are examples, not a default
policy or a coverage checklist. Use the repository's own authority, tools, scope,
and exceptions; keep unadopted suggestions separate from its requirements.

## Follow configured conventions

Suppose the contributor guide already requires the configured formatter and
linter, with exclusions for generated files. Clarify a vague rule such as
"keep formatting consistent" without choosing a new style:

| Rule | How to apply |
| --- | --- |
| Use the repository's configured formatting and lint rules. | Use the commands documented in the contributor guide and the checked-in tool configuration. Preserve the existing exclusions for generated files. Keep formatting changes within the requested scope. |

In a real repository, name the verified command and link its owning guide or
configuration. If the command changes, update that application guidance in place.
An exclusion remains until the repository changes it; a different preferred
formatter is a proposal, not a maintenance edit.

## Match verification to the change

Suppose accepted contribution guidance requires relevant checks before review,
and a separate release guide requires the full suite before release:

| Rule | How to apply |
| --- | --- |
| Verify changed behavior with the relevant existing checks. | Select checks that exercise the affected behavior, including integration or interface checks when the change crosses those boundaries. Report what ran, its result, and what remains unverified. Follow the release guide's full-suite gate when preparing a release. |

Name the repository's actual checks and link the release gate instead of copying
its procedure. When assessing a regression, identify which existing check should
reject it and whether that check actually does. A missing regression check is an
enforcement gap to hand off; it does not automatically justify a new framework or
running every check for every edit.

## Preserve security and data protections

Suppose the repository already requires authorization checks and preservation of
user-owned files during updates. Its security guide documents a separate admin
recovery path:

| Rule | How to apply |
| --- | --- |
| Preserve established authorization and data-loss protections. | For changes to access control, updates, or deletion, retain the existing permission and ownership checks and error handling. Verify the affected allowed and refused cases, including preservation of user-owned data. Keep admin recovery governed by the security guide. |

Link the existing checks, ownership boundary, and recovery guide after inspecting
them. Preserve the recovery exception rather than silently broadening or removing
it. A newly discovered destructive path should be reported with evidence and a
proposed guard; recording the finding alone adopts no new access policy.

Keep each requirement in its existing authoritative document. If these topics
already have rules, improve their application guidance instead of adding parallel
rows or creating another standards document. Preserve unrelated content and
existing agent routing. Distinguish finding a check from running it, and written
requirements from demonstrated enforcement.
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