agentleFS
Sign inStart free
erikdarlingdataerikdarlingdata/DarlingData/.claude/skills/darlingdata-release/SKILL.md

darlingdata-release

Skill730 starsChanged 2 months agoMITView on GitHub

Prepare a DarlingData stored procedure for release with full audit

The file

Show its rules and text

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈14

    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
  1. Distinctive:

    If a file path is given, read it directly

    line 17
  2. Distinctive:

    If a procedure name is given, search under the repository root and common locations

    line 18
  3. Distinctive:

    Read the full source code

    line 19
  4. Distinctive:

    Run the full checklist from the review-sql skill:

    line 22
  5. Distinctive:

    No MERGE, no explicit temp table drops

    line 34
  6. Distinctive:

    Verify the file has proper SET options:

    line 38
  7. Very specific:

    Check for SET XACT_ABORT ON.

    line 43
  8. Distinctive:

    All parameters have inline comments describing their purpose

    line 46
  9. Distinctive:

    Default values are sensible

    line 47
  10. Distinctive:

    Verify no external helper functions, procedures, or views are referenced

    line 61
  11. Distinctive:

    All logic is self-contained within the procedure

    line 62
  12. Distinctive:

    Only references to system DMVs, catalog views, and standard system procedures

    line 63
  13. Distinctive:

    Check for version information

    line 66
  14. Distinctive:

    Check for copyright/attribution comments

    line 67
  15. Distinctive:

    If the procedure is NOT READY, list exactly what needs to change.

    line 78

≈ “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

DarlingData Release Prep

Prepare a stored procedure for public release by running a comprehensive audit.

Target: $ARGUMENTS (procedure name or file path)

Steps

1. Locate the Procedure

  • If a file path is given, read it directly
  • If a procedure name is given, search under the repository root and common locations
  • Read the full source code

2. Style Guide Compliance Audit

Run the full checklist from the review-sql skill:

  • Keywords and functions UPPERCASE
  • Data types lowercase, never abbreviated
  • sysname for object names
  • 4-space indentation
  • Trailing commas
  • Column aliases as name = expression
  • Schema prefixes on all non-temp objects
  • Table aliases with AS keyword
  • Block comments only
  • COUNT_BIG, ROWCOUNT_BIG, CONVERT (not CAST)
  • Proper BEGIN TRY/CATCH pattern
  • No MERGE, no explicit temp table drops
  • Semicolons on statements

3. SET Options Audit

Verify the file has proper SET options:

  • SET ANSI_NULLS ON; before the procedure
  • SET QUOTED_IDENTIFIER ON; before the procedure
  • SET NOCOUNT ON; inside the procedure
  • SET TRANSACTION ISOLATION LEVEL READ UNCOMMITTED; if appropriate
  • Check for SET XACT_ABORT ON; where transactions are used

4. Parameter Review

  • All parameters have inline comments describing their purpose
  • Default values are sensible
  • @help and @debug parameters present
  • Parameter validation section exists

5. Help Section Review

  • Help section exists and is triggered by @help = 1
  • Help text accurately describes the procedure's purpose and parameters

6. Error Handling Review

  • BEGIN TRY / BEGIN CATCH present
  • ROLLBACK in CATCH if transactions are used
  • THROW used to re-raise errors

7. Dependency Check

  • Verify no external helper functions, procedures, or views are referenced
  • All logic is self-contained within the procedure
  • Only references to system DMVs, catalog views, and standard system procedures

8. Version and Header

  • Check for version information
  • Check for copyright/attribution comments

Output Format

Present as a release readiness report:

  1. Release Readiness: READY / NOT READY (with blocking issues)
  2. Issues Found: Grouped by severity (Blocking / Warning / Suggestion)
  3. Checklist Summary: Table showing pass/fail for each audit category
  4. Recommended Fixes: Specific changes needed before release, with line numbers

If the procedure is NOT READY, list exactly what needs to change. If it IS READY, confirm it and suggest committing.

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