applying-wpf-dev-pack-feedback

Solid

Applies one wpf-dev-pack feedback document to the plugin. The maintainer points it at a feedback markdown file (typically delivered via a contributor PR); the skill walks through each item, makes the proposed changes, moves the document into FeedbackDocs/, and appends a row to FeedbackDocs/APPLIED-LOG.md. Use only as a maintainer of the dotnet-with-claudecode repository when reflecting a contributor's feedback md.

Data & Documents 40 stars 6 forks Updated 6 days ago MIT

Install

View on GitHub

Quality Score: 81/100

Stars 20%
54
Recency 20%
100
Frontmatter 20%
40
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# Applying wpf-dev-pack Feedback This skill turns one feedback markdown file (produced by the `/wpf-dev-pack:collecting-wpf-dev-pack-feedback` skill in a foreign WPF session) into concrete changes inside the `wpf-dev-pack` plugin, then records the application in `FeedbackDocs/APPLIED-LOG.md` and parks the source document inside `FeedbackDocs/`. It is the *maintainer counterpart* of the collecting skill. ## When NOT to use this - The feedback document has not been read manually yet — read it first. - The working tree is not clean — apply the feedback against a known baseline so the resulting commit is reviewable. - `$0` was not provided — the skill needs exactly one argument: the path to the feedback markdown file (absolute, or relative to repo root). - More than one feedback document at a time — invoke the skill per file. Batch application is intentionally not supported. ## Workflow Copy this checklist and track progress: ``` Apply Progress: - [ ] Step 1: Validate input and load the feedback md - [ ] Step 2: Plan: review the summary, decide which items to apply - [ ] Step 3: Apply each selected item (one at a time) - [ ] Step 4: Flag whether a release is needed (NEVER bump the version here) - [ ] Step 5: Move the md into FeedbackDocs/ - [ ] Step 6: Append a row to FeedbackDocs/APPLIED-LOG.md - [ ] Step 7: Surface a commit message draft for the maintainer ``` ### Step 1 — Validate input and load Treat `$0` as the path to the feedback markdown file. Reject early ...

Details

Author
christian289
Repository
christian289/dotnet-with-claudecode
Created
7 months ago
Last Updated
6 days ago
Language
C#
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

Data & Documents Solid

collecting-wpf-dev-pack-feedback

Analyzes the current WPF working session and produces an accumulable wpf-dev-pack improvement-feedback markdown file in the current directory. Use when, after doing WPF work with wpf-dev-pack skills/scaffolders in a project OUTSIDE the dotnet-with-claudecode repo, you want to capture anti-patterns you hand-fixed, missing or outdated skill guidance, mistaken or missed triggers, and scaffolder gaps — without editing wpf-dev-pack directly. The output md is meant to be contributed to dotnet-with-claudecode/FeedbackDocs via a pull request.

40 Updated 6 days ago
christian289
Code & Development Listed

workflow-address-feedback

Use when a PR owner wants to address review feedback — fetches outstanding threads and general comments, presents a per-item triage (ADDRESSED / CLARIFIED / DEFERRED), applies fixes via the Edit tool, commits via workflow-commit-and-pr, posts replies via the GitHub API, resolves addressed threads via GraphQL resolveReviewThread (those without a thread are never resolved), and syncs stale PR metadata when drift is detected.

3 Updated yesterday
lugassawan
Data & Documents Listed

feedback

Use this skill when the user says "send feedback", "report a bug", "this didn't work", "I want to suggest a feature", "where do I file an issue for iEvo", or after iEvo has done something the user would want to comment on. Submits feedback about the iEvo plugin — bug reports, feature requests, suggestions, or general comments. Posts as a GitHub issue in `ievo-ai/skills` via `gh` CLI.

0 Updated today
ievo-ai