Skip to content
cccskills
FreePublished on GitHub

test-feature

Acceptance-test newly added features using browser automation, happy-path flows, screenshots, UX notes, and a written report. Use when asked to test a feature, verify a recent UI change, or check whether an app workflow works.

The English summary is being prepared. Showing the original description.

See how to install

Files included (1)

  • SKILL.md1.3 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Feature Acceptance Testing

Use the user's configured browser automation tool to perform acceptance testing on recently added features.

Testing Process

  1. Get Application URL: Ask the user for the URL of the application to test
  2. Handle Authentication: If login screens are encountered, ask the user for guidance
  3. Test Happy Paths: Run through all main user flows for the new features (not intensive QA, just sensible "does this work" testing)
  4. Identify Issues: Document any features not working as expected
  5. UX/UI Review: Note any UX/UI improvements that could be made
  6. Generate Report: Create a comprehensive test report

Report Format

The report should include:

  • List of all features that are not working as expected
  • UX/UI improvement suggestions
  • Save location: Current directory with naming format: test-report-{feature-name}-{YYYY-MM-DD-HH-MM}.md

Execution

Use the browser automation tool to:

  • Navigate through the application
  • Test all happy path scenarios
  • Capture screenshots of issues
  • Document findings in a structured report

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.

The English summary is being prepared. Showing the original description.

SDiamante13/dotfiles11Updated Oct 2, 2026

Rebuilds session context after a clear by reading git history, plans, and beads state. Triggers on 'catch up'.

The English summary is being prepared. Showing the original description.

SDiamante13/dotfiles11Updated Oct 2, 2026

Generate a bullet-point summary of branch changes for a PR description. Triggers on "changelog", "pr summary", "summarize branch", or "/changelog".

The English summary is being prepared. Showing the original description.

SDiamante13/dotfiles11Updated Oct 2, 2026

commit

Free

Commit the current changes with quality checks, status review, staged diff inspection, appropriate tests, and a clear commit message. Use when the user says "commit", "c", asks to make a commit, or wants changes saved in git.

The English summary is being prepared. Showing the original description.

SDiamante13/dotfiles11Updated Oct 2, 2026

Refactor code to remove dead code, useless comments, unused variables, and unused imports. Use when asked to declutter a class, clean up noisy code, remove cruft, or run `/refactor:declutter`.

The English summary is being prepared. Showing the original description.

SDiamante13/dotfiles11Updated Oct 2, 2026

dry

Free

Refactor duplicated code by extracting helpers, shared abstractions, or clearer reusable structure. Use when asked to apply DRY, remove duplication, consolidate repeated logic, or run `/refactor:dry`.

The English summary is being prepared. Showing the original description.

SDiamante13/dotfiles11Updated Oct 2, 2026

See all skills by SDiamante13

Report a problem with this skill