lu-query-manage-schema
Skill2 starsChanged 29 days agoMITView on GitHub
Use lu-query to change Oracle structure in the user's own schema - comments on tables and columns, views, synonyms, sequences, indexes and materialized-view logs. Use when the user asked for a DDL change and you must know its constraints, the columns argument shape, and what Oracle will refuse.
In this repository45 other files it gives its agents.
- AGENTS.mdAGENTS.md
- api-and-interface-designSkill
- browser-testing-with-devtoolsSkill
- ci-cd-and-automationSkill
- code-review-and-qualitySkill
- code-reviewSkill
- code-simplificationSkill
- constraint-driven-developmentSkill
- debugging-and-error-recoverySkill
- deprecation-and-migrationSkill
- documentation-and-adrsSkill
- domain-modelingSkill
- doubt-driven-developmentSkill
- frontend-ui-engineeringSkill
- git-workflow-and-versioningSkill
- grill-meSkill
- grill-with-docsSkill
- implementSkill
- implement-specSkill
- improve-codebase-architectureSkill
- incremental-implementationSkill
- observability-and-instrumentationSkill
- performance-optimizationSkill
- planning-and-task-breakdownSkill
- prSkill
- security-and-hardeningSkill
- setup-matt-pocock-skillsSkill
- shipping-and-launchSkill
- source-driven-developmentSkill
- spec-driven-developmentSkill
- test-driven-developmentSkill
- to-specSkill
- to-ticketsSkill
- using-agent-skillsSkill
- wayfinderSkill
- writing-for-agentsSkill
- lu-query-audit-data-qualitySkill
- lu-query-audit-reportSkill
- lu-query-benchmark-sqlSkill
- lu-query-explore-schemaSkill
- lu-query-plan-data-changesSkill
- lu-query-query-dataSkill
- lu-query-triage-incidentSkill
- lu-query-tune-sqlSkill
- lu-query-use-plsqlSkill
The file
Files
Manage schema objects with lu-query
When to use
- "Document this column", "create a view over these tables", "add an index on (dept_id, salary)", "make a synonym for HR tables".
When not to use
- Row-level changes → lu-query-plan-data-changes.
- Reading existing DDL → lu-query-explore-schema.
- Creating tables, packages or types: no tool does that. PL/SQL source and
CREATE TABLEneed another route (sqlplus, a migration tool, or a DBA); this server is a client, not a migration engine.
Workflow
- Check what exists.
table_exists,list_indexes,search_objectsbefore creating anything; useget_ddlfor the current definition. - Prefer create-or-replace semantics.
create_or_replace_viewandcreate_synonymreplace silently;create_sequenceandcreate_indexfail if the name exists (drop first, with the user's approval). - Shape arguments correctly. Indexes take
columnsas an array;indexis the index name andtableSchemais the table's owner - different from theschemaargument that names the target schema. - Respect ownership. Comment tools only work on objects the connected user owns (there is no system privilege for commenting someone else's table). Views and sequences require
CREATE ANY …for other schemas. - Verify. Re-read with
list_indexes/list_views/get_ddland quote the result.
Tool reference
| Tool | Signature | Notes |
comment_on_table | table*, comment*, schema? | replaces the comment |
comment_on_column | table*, column*, comment*, schema? | replaces the comment |
create_or_replace_view | view*, selectBody*, schema? | selectBody is a SELECT without the trailing ; |
create_synonym | synonym*, targetSchema*, targetName*, isPublic? | private by default |
create_sequence | sequence*, startWith?, incrementBy?, cache?, schema? | fails if the name exists |
create_index | table*, columns* (array), index*, tableSchema*, unique?, schema? | tableSchema = owner of the table |
create_mview_log | table*, withPrimaryKey?, withRowid?, includingNewValues?, schema? | required before fast refresh |
Details: references/tools.md. Verified transcripts: references/examples.md.
Reading results correctly
Each tool returns a single confirmation line such as Index DEVUSER.SKL_EMP_EMAIL_IX created on DEVUSER.SKL_EMP. - one call, one object. There is no batch mode; parallel calls are fine because each is its own transaction.
Safety
- DDL auto-commits and cannot be rolled back through this server. Confirm the target schema out loud before creating.
- Names go through an identifier allow-list (
^[A-Za-z][A-Za-z0-9_$#]{0,127}$); quoted, mixed-case or exotic names will be rejected. - Creating a public synonym (
isPublic: true) exposes the object to every user - confirm intent.
Failure recovery
| Symptom | Cause | Action |
ORA-01031 insufficient privileges | no CREATE ANY … and not owner | ask for the grant; do not retry |
ORA-00955 name already used | object exists | inspect with search_objects; replace (view/synonym) or ask before dropping |
ORA-01031 on comments | object owned by another user | comments are owner-only |
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
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.

