devskill 2.0.7 → 2.0.8

package/skills/write-coding-standards-from-file/SKILL.md

@@ -0,0 +1,316 @@
+---
+name: write-coding-standards-from-file
+description: 'Write a coding standards document for a project using the coding styles from the file(s) and/or folder(s) passed as arguments in the prompt.'
+---
+
+# Write Coding Standards From File
+
+Use the existing syntax of the file(s) to establish the standards and style guides for the project. If more than one file or a folder is passed, loop through each file or files in the folder, appending the file's data to temporary memory or a file, then when complete use temporary data as a single instance; as if it were the file name to base the standards and style guideline on.
+
+## Rules and Configuration
+
+Below is a set of quasi-configuration `boolean` and `string[]` variables. Conditions for handling `true`, or other values for each variable are under the level two heading `## Variable and Parameter Configuration Conditions`.
+
+Parameters for the prompt have a text definition. There is one required parameter **`${fileName}`**, and several optional parameters **`${folderName}`**, **`${instructions}`**, and any **`[configVariableAsParameter]`**.
+
+### Configuration Variables
+
+* addStandardsTest = false;
+* addToREADME = false;
+* addToREADMEInsertions = ["atBegin", "middle", "beforeEnd", "bestFitUsingContext"];
+  - Default to **beforeEnd**.
+* createNewFile = true;
+* fetchStyleURL = true;
+* findInconsistencies = true;
+* fixInconsistencies = true;
+* newFileName = ["CONTRIBUTING.md", "STYLE.md", "CODE_OF_CONDUCT.md", "CODING_STANDARDS.md", "DEVELOPING.md", "CONTRIBUTION_GUIDE.md", "GUIDELINES.md", "PROJECT_STANDARDS.md", "BEST_PRACTICES.md", "HACKING.md"];
+  - For each file in `${newFileName}`, if file does not exist, use that file name and `break`, else continue to next file name of `${newFileName}`.
+* outputSpecToPrompt = false;
+* useTemplate = "verbose"; // or "v"
+  - Possible values are `[["v", "verbose"], ["m", "minimal"], ["b", "best fit"], ["custom"]]`.
+  - Selects one of the two example templates at the bottom of prompt file under the level two heading `## Coding Standards Templates`, or use another composition that is a better fit.
+  - If **custom**, then apply per request.
+
+### Configuration Variables as Prompt Parameters
+
+If any of the variable names are passed to prompt as-is, or as a similar but clearly related text value, then override the default variable value with the value passed to prompt.
+
+### Prompt Parameters
+
+* **fileName** = The name of the file that will be analyzed in terms of: indentation, variable naming, commenting, conditional procedures, functional procedures, and other syntax related data for the coding language of the file.
+* folderName = The name of the folder that will be used to extract data from multiple files into one aggregated dataset that will be analyzed in terms of: indentation, variable naming, commenting, conditional procedures, functional procedures, and other syntax related data for the coding language of the files.
+* instructions = Additional instructions, rules, and procedures that will be provided for unique cases.
+* [configVariableAsParameter] = If passed will override the default state of the configuration variable. Example:
+  - useTemplate = If passed will override the configuration `${useTemplate}` default. Values are `[["v", "verbose"], ["m", "minimal"], ["b", "best fit"]]`.
+
+#### Required and Optional Parameters
+
+* **fileName** - required
+* folderName - *optional*
+* instructions - *optional*
+* [configVariableAsParameter] - *optional*
+
+## Variable and Parameter Configuration Conditions
+
+### `${fileName}.length > 1 || ${folderName} != undefined`
+
+* If true, toggle `${fixInconsistencies}` to false.
+
+### `${addToREADME} == true`
+
+* Insert the coding standards into the `README.md` instead of outputting to the prompt or creating a new file.
+* If true, toggle both `${createNewFile}` and `${outputSpecToPrompt}` to false.
+
+### `${addToREADMEInsertions} == "atBegin"`
+
+* If `${addToREADME}` is true, then insert the coding standards data at the **beginning** of the `README.md` file after the title.
+
+### `${addToREADMEInsertions} == "middle"`
+
+* If `${addToREADME}` is true, then insert the coding standards data at the **middle** of the `README.md` file, changing the standards title heading to match that of the `README.md` composition.
+
+### `${addToREADMEInsertions} == "beforeEnd"`
+
+* If `${addToREADME}` is true, then insert the coding standards data at the **end** of the `README.md` file, inserting a new line after the last character, then inserting the data on a new line.
+
+### `${addToREADMEInsertions} == "bestFitUsingContext"`
+
+* If `${addToREADME}` is true, then insert the coding standards data at the **best fitting line** of the `README.md` file in regards to the context of the `README.md` composition and flow of data.
+
+### `${addStandardsTest} == true`
+
+* Once the coding standards file is complete, write a test file to ensure the file or files passed to it adhere to the coding standards.
+
+### `${createNewFile} == true`
+
+* Create a new file using the value, or one of the possible values, from `${newFileName}`.
+* If true, toggle both `${outputSpecToPrompt}` and `${addToREADME}` to false.
+
+### `${fetchStyleURL} == true`
+
+* Additionally use the data fetched from the links nested under level three heading `### Fetch Links` as context for creating standards, specifications, and styling data for the new file, prompt, or `README.md`.
+* For each relevant item in `### Fetch Links`, run `#fetch ${item}`.
+
+### `${findInconsistencies} == true`
+
+* Evaluate syntax related to indentations, line-breaks, comments, conditional and function nesting, quotation wrappers i.e. `'` or `"` for strings, etc., and categorize.
+* For each category, make a count, and if one item does not match the majority of the count, then commit to temporary memory.
+* Depending on the status of `${fixInconsistencies}`, either edit and fix the low count categories to match the majority, or output to prompt inconsistencies stored in temporary memory.
+
+### `${fixInconsistencies} == true`
+
+* Edit and fix the low count categories of syntax data to match the majority of corresponding syntax data using inconsistencies stored in temporary memory.
+
+### `typeof ${newFileName} == "string"`
+
+* If specifically defined as a `string`, create a new file using the value from `${newFileName}`.
+
+### `typeof ${newFileName} != "string"`
+
+* If **NOT** specifically defined as a `string`, but instead an `object` or an array, create a new file using a value from `${newFileName}` by applying this rule:
+  - For each file name in `${newFileName}`, if file does not exist, use that file name and `break`, else continue to the next.
+
+### `${outputSpecToPrompt} == true`
+
+* Output the coding standards to the prompt instead of creating a file or adding to README.
+* If true, toggle both `${createNewFile}` and `${addToREADME}` to false.
+
+### `${useTemplate} == "v" || ${useTemplate} == "verbose"`
+
+* Use data under the level three heading `### "v", "verbose"` as guiding template when composing the data for coding standards.
+
+### `${useTemplate} == "m" || ${useTemplate} == "minimal"`
+
+* Use data under the level three heading `### "m", "minimal"` as guiding template when composing the data for coding standards.
+
+### `${useTemplate} == "b" || ${useTemplate} == "best"`
+
+* Use either the data under the level three heading `### "v", "verbose"` or `### "m", "minimal"`, depending on the data extracted from `${fileName}`, and use the best fit as guiding template when composing the data for coding standards.
+
+### `${useTemplate} == "custom" || ${useTemplate} == "<ANY_NAME>"`
+
+* Use the custom prompt, instructions, template, or other data passed as guiding template when composing the data for coding standards.
+
+## **if** `${fetchStyleURL} == true`
+
+Depending on the programming language, for each link in list below, run `#fetch (URL)`, if programming language is `${fileName} == [<Language> Style Guide]`.
+
+### Fetch Links
+
+- [C Style Guide](https://users.ece.cmu.edu/~eno/coding/CCodingStandard.html)
+- [C# Style Guide](https://learn.microsoft.com/en-us/dotnet/csharp/fundamentals/coding-style/coding-conventions)
+- [C++ Style Guide](https://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines)
+- [Go Style Guide](https://github.com/golang-standards/project-layout)
+- [Java Style Guide](https://coderanch.com/wiki/718799/Style)
+- [AngularJS App Style Guide](https://github.com/mgechev/angularjs-style-guide)
+- [jQuery Style Guide](https://contribute.jquery.org/style-guide/js/)
+- [JavaScript Style Guide](https://www.w3schools.com/js/js_conventions.asp)
+- [JSON Style Guide](https://google.github.io/styleguide/jsoncstyleguide.xml)
+- [Kotlin Style Guide](https://kotlinlang.org/docs/coding-conventions.html)
+- [Markdown Style Guide](https://cirosantilli.com/markdown-style-guide/)
+- [Perl Style Guide](https://perldoc.perl.org/perlstyle)
+- [PHP Style Guide](https://phptherightway.com/)
+- [Python Style Guide](https://peps.python.org/pep-0008/)
+- [Ruby Style Guide](https://rubystyle.guide/)
+- [Rust Style Guide](https://github.com/rust-lang/rust/tree/HEAD/src/doc/style-guide/src)
+- [Swift Style Guide](https://www.swift.org/documentation/api-design-guidelines/)
+- [TypeScript Style Guide](https://www.typescriptlang.org/docs/handbook/declaration-files/do-s-and-don-ts.html)
+- [Visual Basic Style Guide](https://en.wikibooks.org/wiki/Visual_Basic/Coding_Standards)
+- [Shell Script Style Guide](https://google.github.io/styleguide/shellguide.html)
+- [Git Usage Style Guide](https://github.com/agis/git-style-guide)
+- [PowerShell Style Guide](https://github.com/PoshCode/PowerShellPracticeAndStyle)
+- [CSS](https://cssguidelin.es/)
+- [Sass Style Guide](https://sass-guidelin.es/)
+- [HTML Style Guide](https://github.com/marcobiedermann/html-style-guide)
+- [Linux kernel Style Guide](https://www.kernel.org/doc/html/latest/process/coding-style.html)
+- [Node.js Style Guide](https://github.com/felixge/node-style-guide)
+- [SQL Style Guide](https://www.sqlstyle.guide/)
+- [Angular Style Guide](https://angular.dev/style-guide)
+- [Vue Style Guide](https://vuejs.org/style-guide/rules-strongly-recommended.html)
+- [Django Style Guide](https://docs.djangoproject.com/en/dev/internals/contributing/writing-code/coding-style/)
+- [SystemVerilog Style Guide](https://github.com/lowRISC/style-guides/blob/master/VerilogCodingStyle.md)
+
+## Coding Standards Templates
+
+### `"m", "minimal"`
+
+```text
+    ```markdown
+    ## 1. Introduction
+    *   **Purpose:** Briefly explain why the coding standards are being established (e.g., to improve code quality, maintainability, and team collaboration).
+    *   **Scope:** Define which languages, projects, or modules this specification applies to.
+
+    ## 2. Naming Conventions
+    *   **Variables:** `camelCase`
+    *   **Functions/Methods:** `PascalCase` or `camelCase`.
+    *   **Classes/Structs:** `PascalCase`.
+    *   **Constants:** `UPPER_SNAKE_CASE`.
+
+    ## 3. Formatting and Style
+    *   **Indentation:** Use 4 spaces per indent (or tabs).
+    *   **Line Length:** Limit lines to a maximum of 80 or 120 characters.
+    *   **Braces:** Use the "K&R" style (opening brace on the same line) or the "Allman" style (opening brace on a new line).
+    *   **Blank Lines:** Specify how many blank lines to use for separating logical blocks of code.
+
+    ## 4. Commenting
+    *   **Docstrings/Function Comments:** Describe the function's purpose, parameters, and return values.
+    *   **Inline Comments:** Explain complex or non-obvious logic.
+    *   **File Headers:** Specify what information should be included in a file header, such as author, date, and file description.
+
+    ## 5. Error Handling
+    *   **General:** How to handle and log errors.
+    *   **Specifics:** Which exception types to use, and what information to include in error messages.
+
+    ## 6. Best Practices and Anti-Patterns
+    *   **General:** List common anti-patterns to avoid (e.g., global variables, magic numbers).
+    *   **Language-specific:** Specific recommendations based on the project's programming language.
+
+    ## 7. Examples
+    *   Provide a small code example demonstrating the correct application of the rules.
+    *   Provide a small code example of an incorrect implementation and how to fix it.
+
+    ## 8. Contribution and Enforcement
+    *   Explain how the standards are to be enforced (e.g., via code reviews).
+    *   Provide a guide for contributing to the standards document itself.
+    ```
+```
+
+### `"v", verbose"`
+
+```text
+    ```markdown
+
+    # Style Guide
+
+    This document defines the style and conventions used in this project.
+    All contributions should follow these rules unless otherwise noted.
+
+    ## 1. General Code Style
+
+    - Favor clarity over brevity.
+    - Keep functions and methods small and focused.
+    - Avoid repeating logic; prefer shared helpers/utilities.
+    - Remove unused variables, imports, code paths, and files.
+
+    ## 2. Naming Conventions
+
+    Use descriptive names. Avoid abbreviations unless well-known.
+
+    | Item            | Convention           | Example            |
+    |-----------------|----------------------|--------------------|
+    | Variables       | `lower_snake_case`   | `buffer_size`      |
+    | Functions       | `lower_snake_case()` | `read_file()`      |
+    | Constants       | `UPPER_SNAKE_CASE`   | `MAX_RETRIES`      |
+    | Types/Structs   | `PascalCase`         | `FileHeader`       |
+    | File Names      | `lower_snake_case`   | `file_reader.c`    |
+
+    ## 3. Formatting Rules
+
+    - Indentation: **4 spaces**
+    - Line length: **max 100 characters**
+    - Encoding: **UTF-8**, no BOM
+    - End files with a newline
+
+    ### Braces (example in C, adjust for your language)
+
+        ```c
+        if (condition) {
+            do_something();
+        } else {
+            do_something_else();
+        }
+        ```
+
+    ### Spacing
+
+    - One space after keywords: `if (x)`, not `if(x)`
+    - One blank line between top-level functions
+
+    ## 4. Comments & Documentation
+
+    - Explain *why*, not *what*, unless intent is unclear.
+    - Keep comments up-to-date as code changes.
+    - Public functions should include a short description of purpose and parameters.
+
+    Recommended tags:
+
+        ```text
+        TODO: follow-up work
+        FIXME: known incorrect behavior
+        NOTE: non-obvious design decision
+        ```
+
+    ## 5. Error Handling
+
+    - Handle error conditions explicitly.
+    - Avoid silent failures; either return errors or log them appropriately.
+    - Clean up resources (files, memory, handles) before returning on failure.
+
+    ## 6. Commit & Review Practices
+
+    ### Commits
+    - One logical change per commit.
+    - Write clear commit messages:
+
+        ```text
+        Short summary (max ~50 chars)
+        Optional longer explanation of context and rationale.
+        ```
+
+    ### Reviews
+    - Keep pull requests reasonably small.
+    - Be respectful and constructive in review discussions.
+    - Address requested changes or explain if you disagree.
+
+    ## 7. Tests
+
+    - Write tests for new functionality.
+    - Tests should be deterministic (no randomness without seeding).
+    - Prefer readable test cases over complex test abstraction.
+
+    ## 8. Changes to This Guide
+
+    Style evolves.
+    Propose improvements by opening an issue or sending a patch updating this document.
+    ```
+```

package/skills/write-coding-standards-from-file/SYNC.md

@@ -0,0 +1,5 @@
+# Sync Info
+
+- **Source:** `vendor/awesome-copilot/skills/write-coding-standards-from-file`
+- **Git SHA:** `23fb7006c132a0bba75b0e5af7a35cab11272812`
+- **Synced:** 2026-03-24

package/skills/webapp-testing/LICENSE.txt

@@ -1,202 +0,0 @@
-
-                                 Apache License
-                           Version 2.0, January 2004
-                        http://www.apache.org/licenses/
-
-   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
-   1. Definitions.
-
-      "License" shall mean the terms and conditions for use, reproduction,
-      and distribution as defined by Sections 1 through 9 of this document.
-
-      "Licensor" shall mean the copyright owner or entity authorized by
-      the copyright owner that is granting the License.
-
-      "Legal Entity" shall mean the union of the acting entity and all
-      other entities that control, are controlled by, or are under common
-      control with that entity. For the purposes of this definition,
-      "control" means (i) the power, direct or indirect, to cause the
-      direction or management of such entity, whether by contract or
-      otherwise, or (ii) ownership of fifty percent (50%) or more of the
-      outstanding shares, or (iii) beneficial ownership of such entity.
-
-      "You" (or "Your") shall mean an individual or Legal Entity
-      exercising permissions granted by this License.
-
-      "Source" form shall mean the preferred form for making modifications,
-      including but not limited to software source code, documentation
-      source, and configuration files.
-
-      "Object" form shall mean any form resulting from mechanical
-      transformation or translation of a Source form, including but
-      not limited to compiled object code, generated documentation,
-      and conversions to other media types.
-
-      "Work" shall mean the work of authorship, whether in Source or
-      Object form, made available under the License, as indicated by a
-      copyright notice that is included in or attached to the work
-      (an example is provided in the Appendix below).
-
-      "Derivative Works" shall mean any work, whether in Source or Object
-      form, that is based on (or derived from) the Work and for which the
-      editorial revisions, annotations, elaborations, or other modifications
-      represent, as a whole, an original work of authorship. For the purposes
-      of this License, Derivative Works shall not include works that remain
-      separable from, or merely link (or bind by name) to the interfaces of,
-      the Work and Derivative Works thereof.
-
-      "Contribution" shall mean any work of authorship, including
-      the original version of the Work and any modifications or additions
-      to that Work or Derivative Works thereof, that is intentionally
-      submitted to Licensor for inclusion in the Work by the copyright owner
-      or by an individual or Legal Entity authorized to submit on behalf of
-      the copyright owner. For the purposes of this definition, "submitted"
-      means any form of electronic, verbal, or written communication sent
-      to the Licensor or its representatives, including but not limited to
-      communication on electronic mailing lists, source code control systems,
-      and issue tracking systems that are managed by, or on behalf of, the
-      Licensor for the purpose of discussing and improving the Work, but
-      excluding communication that is conspicuously marked or otherwise
-      designated in writing by the copyright owner as "Not a Contribution."
-
-      "Contributor" shall mean Licensor and any individual or Legal Entity
-      on behalf of whom a Contribution has been received by Licensor and
-      subsequently incorporated within the Work.
-
-   2. Grant of Copyright License. Subject to the terms and conditions of
-      this License, each Contributor hereby grants to You a perpetual,
-      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
-      copyright license to reproduce, prepare Derivative Works of,
-      publicly display, publicly perform, sublicense, and distribute the
-      Work and such Derivative Works in Source or Object form.
-
-   3. Grant of Patent License. Subject to the terms and conditions of
-      this License, each Contributor hereby grants to You a perpetual,
-      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
-      (except as stated in this section) patent license to make, have made,
-      use, offer to sell, sell, import, and otherwise transfer the Work,
-      where such license applies only to those patent claims licensable
-      by such Contributor that are necessarily infringed by their
-      Contribution(s) alone or by combination of their Contribution(s)
-      with the Work to which such Contribution(s) was submitted. If You
-      institute patent litigation against any entity (including a
-      cross-claim or counterclaim in a lawsuit) alleging that the Work
-      or a Contribution incorporated within the Work constitutes direct
-      or contributory patent infringement, then any patent licenses
-      granted to You under this License for that Work shall terminate
-      as of the date such litigation is filed.
-
-   4. Redistribution. You may reproduce and distribute copies of the
-      Work or Derivative Works thereof in any medium, with or without
-      modifications, and in Source or Object form, provided that You
-      meet the following conditions:
-
-      (a) You must give any other recipients of the Work or
-          Derivative Works a copy of this License; and
-
-      (b) You must cause any modified files to carry prominent notices
-          stating that You changed the files; and
-
-      (c) You must retain, in the Source form of any Derivative Works
-          that You distribute, all copyright, patent, trademark, and
-          attribution notices from the Source form of the Work,
-          excluding those notices that do not pertain to any part of
-          the Derivative Works; and
-
-      (d) If the Work includes a "NOTICE" text file as part of its
-          distribution, then any Derivative Works that You distribute must
-          include a readable copy of the attribution notices contained
-          within such NOTICE file, excluding those notices that do not
-          pertain to any part of the Derivative Works, in at least one
-          of the following places: within a NOTICE text file distributed
-          as part of the Derivative Works; within the Source form or
-          documentation, if provided along with the Derivative Works; or,
-          within a display generated by the Derivative Works, if and
-          wherever such third-party notices normally appear. The contents
-          of the NOTICE file are for informational purposes only and
-          do not modify the License. You may add Your own attribution
-          notices within Derivative Works that You distribute, alongside
-          or as an addendum to the NOTICE text from the Work, provided
-          that such additional attribution notices cannot be construed
-          as modifying the License.
-
-      You may add Your own copyright statement to Your modifications and
-      may provide additional or different license terms and conditions
-      for use, reproduction, or distribution of Your modifications, or
-      for any such Derivative Works as a whole, provided Your use,
-      reproduction, and distribution of the Work otherwise complies with
-      the conditions stated in this License.
-
-   5. Submission of Contributions. Unless You explicitly state otherwise,
-      any Contribution intentionally submitted for inclusion in the Work
-      by You to the Licensor shall be under the terms and conditions of
-      this License, without any additional terms or conditions.
-      Notwithstanding the above, nothing herein shall supersede or modify
-      the terms of any separate license agreement you may have executed
-      with Licensor regarding such Contributions.
-
-   6. Trademarks. This License does not grant permission to use the trade
-      names, trademarks, service marks, or product names of the Licensor,
-      except as required for reasonable and customary use in describing the
-      origin of the Work and reproducing the content of the NOTICE file.
-
-   7. Disclaimer of Warranty. Unless required by applicable law or
-      agreed to in writing, Licensor provides the Work (and each
-      Contributor provides its Contributions) on an "AS IS" BASIS,
-      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
-      implied, including, without limitation, any warranties or conditions
-      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
-      PARTICULAR PURPOSE. You are solely responsible for determining the
-      appropriateness of using or redistributing the Work and assume any
-      risks associated with Your exercise of permissions under this License.
-
-   8. Limitation of Liability. In no event and under no legal theory,
-      whether in tort (including negligence), contract, or otherwise,
-      unless required by applicable law (such as deliberate and grossly
-      negligent acts) or agreed to in writing, shall any Contributor be
-      liable to You for damages, including any direct, indirect, special,
-      incidental, or consequential damages of any character arising as a
-      result of this License or out of the use or inability to use the
-      Work (including but not limited to damages for loss of goodwill,
-      work stoppage, computer failure or malfunction, or any and all
-      other commercial damages or losses), even if such Contributor
-      has been advised of the possibility of such damages.
-
-   9. Accepting Warranty or Additional Liability. While redistributing
-      the Work or Derivative Works thereof, You may choose to offer,
-      and charge a fee for, acceptance of support, warranty, indemnity,
-      or other liability obligations and/or rights consistent with this
-      License. However, in accepting such obligations, You may act only
-      on Your own behalf and on Your sole responsibility, not on behalf
-      of any other Contributor, and only if You agree to indemnify,
-      defend, and hold each Contributor harmless for any liability
-      incurred by, or claims asserted against, such Contributor by reason
-      of your accepting any such warranty or additional liability.
-
-   END OF TERMS AND CONDITIONS
-
-   APPENDIX: How to apply the Apache License to your work.
-
-      To apply the Apache License to your work, attach the following
-      boilerplate notice, with the fields enclosed by brackets "[]"
-      replaced with your own identifying information. (Don't include
-      the brackets!)  The text should be enclosed in the appropriate
-      comment syntax for the file format. We also recommend that a
-      file or class name and description of purpose be included on the
-      same "printed page" as the copyright notice for easier
-      identification within third-party archives.
-
-   Copyright [yyyy] [name of copyright owner]
-
-   Licensed under the Apache License, Version 2.0 (the "License");
-   you may not use this file except in compliance with the License.
-   You may obtain a copy of the License at
-
-       http://www.apache.org/licenses/LICENSE-2.0
-
-   Unless required by applicable law or agreed to in writing, software
-   distributed under the License is distributed on an "AS IS" BASIS,
-   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-   See the License for the specific language governing permissions and
-   limitations under the License.

package/skills/webapp-testing/examples/console_logging.py

@@ -1,35 +0,0 @@
-from playwright.sync_api import sync_playwright
-
-# Example: Capturing console logs during browser automation
-
-url = 'http://localhost:5173'  # Replace with your URL
-
-console_logs = []
-
-with sync_playwright() as p:
-    browser = p.chromium.launch(headless=True)
-    page = browser.new_page(viewport={'width': 1920, 'height': 1080})
-
-    # Set up console log capture
-    def handle_console_message(msg):
-        console_logs.append(f"[{msg.type}] {msg.text}")
-        print(f"Console: [{msg.type}] {msg.text}")
-
-    page.on("console", handle_console_message)
-
-    # Navigate to page
-    page.goto(url)
-    page.wait_for_load_state('networkidle')
-
-    # Interact with the page (triggers console logs)
-    page.click('text=Dashboard')
-    page.wait_for_timeout(1000)
-
-    browser.close()
-
-# Save console logs to file
-with open('/mnt/user-data/outputs/console.log', 'w') as f:
-    f.write('\n'.join(console_logs))
-
-print(f"\nCaptured {len(console_logs)} console messages")
-print(f"Logs saved to: /mnt/user-data/outputs/console.log")

package/skills/webapp-testing/examples/element_discovery.py

@@ -1,40 +0,0 @@
-from playwright.sync_api import sync_playwright
-
-# Example: Discovering buttons and other elements on a page
-
-with sync_playwright() as p:
-    browser = p.chromium.launch(headless=True)
-    page = browser.new_page()
-
-    # Navigate to page and wait for it to fully load
-    page.goto('http://localhost:5173')
-    page.wait_for_load_state('networkidle')
-
-    # Discover all buttons on the page
-    buttons = page.locator('button').all()
-    print(f"Found {len(buttons)} buttons:")
-    for i, button in enumerate(buttons):
-        text = button.inner_text() if button.is_visible() else "[hidden]"
-        print(f"  [{i}] {text}")
-
-    # Discover links
-    links = page.locator('a[href]').all()
-    print(f"\nFound {len(links)} links:")
-    for link in links[:5]:  # Show first 5
-        text = link.inner_text().strip()
-        href = link.get_attribute('href')
-        print(f"  - {text} -> {href}")
-
-    # Discover input fields
-    inputs = page.locator('input, textarea, select').all()
-    print(f"\nFound {len(inputs)} input fields:")
-    for input_elem in inputs:
-        name = input_elem.get_attribute('name') or input_elem.get_attribute('id') or "[unnamed]"
-        input_type = input_elem.get_attribute('type') or 'text'
-        print(f"  - {name} ({input_type})")
-
-    # Take screenshot for visual reference
-    page.screenshot(path='/tmp/page_discovery.png', full_page=True)
-    print("\nScreenshot saved to /tmp/page_discovery.png")
-
-    browser.close()

package/skills/webapp-testing/examples/static_html_automation.py

@@ -1,33 +0,0 @@
-from playwright.sync_api import sync_playwright
-import os
-
-# Example: Automating interaction with static HTML files using file:// URLs
-
-html_file_path = os.path.abspath('path/to/your/file.html')
-file_url = f'file://{html_file_path}'
-
-with sync_playwright() as p:
-    browser = p.chromium.launch(headless=True)
-    page = browser.new_page(viewport={'width': 1920, 'height': 1080})
-
-    # Navigate to local HTML file
-    page.goto(file_url)
-
-    # Take screenshot
-    page.screenshot(path='/mnt/user-data/outputs/static_page.png', full_page=True)
-
-    # Interact with elements
-    page.click('text=Click Me')
-    page.fill('#name', 'John Doe')
-    page.fill('#email', 'john@example.com')
-
-    # Submit form
-    page.click('button[type="submit"]')
-    page.wait_for_timeout(500)
-
-    # Take final screenshot
-    page.screenshot(path='/mnt/user-data/outputs/after_submit.png', full_page=True)
-
-    browser.close()
-
-print("Static HTML automation completed!")