Kashyap-001Kashyap-001/second-brain-template/.agents/skills/feature-guardian/skill.md

feature-guardian

Skill0 starsChanged 4 months agoMITView on GitHub

Compare an old module and a migrated module to detect lost features, missing logic, and behavioral differences. Never assume migration success means functionality is preserved.

In this repository17 other files it gives its agents.
- .agents/AGENTS.mdAGENTS.md
- .claude/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- brain-syncSkill
- feature-restorerSkill
- find-skillsSkill
- frontend-designSkill
- git-advancedSkill
- obsidian-vaultSkill
- safe-workflowSkill
- security-auditSkill
- session-wrapSkill
- spec-creationSkill
- systematic-debuggingSkill
- testing-patternsSkill
- vault-prunerSkill
- graphifySkill

The file

Show its rules and text

We split this skill into the rules it gives an agent

14 rules. About 0 are common, 13 are distinctive, and 1 is very specific to this project.

≈0
Common · estimate
Many files like this have a rule of this kind.
≈13
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific

Distinctive:
Never assume that successful installation means a successful migration.
line 23
Very specific:
create/write/unlink overrides
line 51
Distinctive:
Never assume deletion was intentional.
line 201
Distinctive:
Never delete features yourself.
line 203
Distinctive:
Only compare and report.
line 207
Distinctive:
Always execute the automated audit script first to programmatically compile structural differences:
line 217
Distinctive:
Use this output as your structural baseline for missing models, fields, and custom methods.
line 221
Distinctive:
Search the current directory.
line 223
Distinctive:
If a sibling directory contains:
line 225
Distinctive:
Treat the old module as the source of truth.
line 247
Distinctive:
Before reporting missing features:
line 355
Distinctive:
If a rename or removal is documented there, do not report it as missing.
line 361
Distinctive:
If the ledger says:
line 374
Distinctive:
Treat this as preserved functionality, not a missing feature.
line 378

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.

Files

skill.md

Inputs

OLD_MODULE = source version (Odoo 17/18)

NEW_MODULE = migrated Odoo 19 version

Never assume that successful installation means a successful migration.

Phase 1 — Inventory Old Module

Build a complete inventory.

Models

model names
inherited models
transient models

Fields

field names
types
computed fields
related fields
default values
constraints

Methods

button methods
onchange methods
compute methods
create/write/unlink overrides
cron methods

Views

form views
list/tree views
search views
kanban views

Buttons

For every button record:

string
method called
visibility conditions

Menus

root menus
actions
hierarchy

Security

groups
access rights
record rules

Reports

qweb reports
report actions

Automations

server actions
scheduled actions

Phase 2 — Inventory Migrated Module

Build the same inventory.

Phase 3 — Compare

Look for:

Missing Models

FAIL if any model disappeared.

Missing Fields

FAIL if fields disappeared.

Ignore intentional renames documented in the ledger.

Missing Methods

FAIL if:

action_confirm
action_cancel
create/write overrides
compute methods

disappeared.

Missing Buttons

FAIL if button exists in old module but not new.

Broken Button Wiring

FAIL if button exists but method no longer exists.

Missing Menus

FAIL if menu hierarchy changed unintentionally.

Missing Reports

FAIL if reports disappeared.

Missing Security

FAIL if groups or access rules disappeared.

Missing Cron Jobs

FAIL if scheduled actions disappeared.

Missing Server Actions

FAIL if server actions disappeared.

Constraint Differences

Report changes.

Business Logic Differences

Detect:

removed validations
removed compute logic
removed workflows
removed onchange behavior

Output

PASS

FAIL

Missing Features

exact feature
file
why it matters

Broken Wiring

button
action
menu
report

Behavior Differences

old behavior
new behavior

Recommended Fixes

Provide exact files that should be inspected.

Rules

Never assume deletion was intentional.

Never delete features yourself.

Never rewrite code.

Only compare and report.

Be paranoid.

A module that installs successfully can still be functionally broken.

Auto-Discovery & Execution Rules

Before comparison:

Always execute the automated audit script first to programmatically compile structural differences:
```
python3 <VAULT_ROOT>/.agents/skills/feature-guardian/scripts/audit_diff.py <old_module_dir> <new_module_dir>
```
Use this output as your structural baseline for missing models, fields, and custom methods.
Search the current directory.
If a sibling directory contains:

old_
_old
backup
legacy
v17
v18

assume it is the reference module.

Examples:

my_module old_my_module

sale_custom sale_custom_old

estate estate_v18

Treat the old module as the source of truth.
Compare:

models
fields
methods
compute fields
constraints
views
buttons
actions
menus
reports
security
cron jobs
server actions

Produce a Feature Loss Report.

Severity Levels

CRITICAL

Missing:

model
field
method
button
report
menu
security rule

WARNING

Behavior changed:

compute logic
onchange logic
validations
constraints

INFO

Syntax changed but functionality preserved.

Output Example

FAIL

CRITICAL

models/milk_batch.py

Missing method:

action_confirm_batch()

Reason:

Button "Confirm Batch" still exists but the method no longer exists.

views/milk_batch_views.xml

Missing button:

Confirm Batch

security/ir.model.access.csv

Manager access removed.

WARNING

_compute_total_quantity()

Logic differs from old version.

Old:

sum(line.qty)

New:

sum(line.quantity)

Possible business behavior change.

Overall Result:

Migration completed successfully but functionality is NOT equivalent to the old module.

Ignore intentional differences

Before reporting missing features:

Read:

Mistakes/[MODULE]_ledger.md

If a rename or removal is documented there, do not report it as missing.

Example:

Old field:

customer_id

New field:

partner_id

If the ledger says:

customer_id → partner_id

Treat this as preserved functionality, not a missing feature.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

It worked
Partly
It didn't

What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free