Skip to content

docs: add lfx-pr-resolve skill to README#49

Open
asithade wants to merge 2 commits intomainfrom
docs/add-lfx-pr-resolve-to-readme
Open

docs: add lfx-pr-resolve skill to README#49
asithade wants to merge 2 commits intomainfrom
docs/add-lfx-pr-resolve-to-readme

Conversation

@asithade
Copy link
Copy Markdown
Contributor

Summary

  • Added /lfx-pr-resolve documentation to all 6 sections of the README where it was missing: verification list, architecture diagram, skill overview table, skill details, typical workflows, and project structure
  • The skill was fully implemented (595-line SKILL.md) and routable from /lfx, but not visible to users reading the README

The lfx-pr-resolve skill was fully implemented but missing from the
README documentation. Added entries across all relevant sections:
verification list, architecture diagram, skill overview table, skill
details, typical workflows, and project structure.

Signed-off-by: Asitha de Silva <asithade@gmail.com>
Copilot AI review requested due to automatic review settings April 14, 2026 16:57
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR updates the root README to surface the already-implemented /lfx-pr-resolve skill so users can discover it via the main documentation entry points.

Changes:

  • Added /lfx-pr-resolve to the “Verify” skill list and architecture diagram.
  • Added /lfx-pr-resolve to the Skill Overview table and the Skill Details section (including workflow + key behaviors).
  • Added /lfx-pr-resolve to Typical Workflows and Project Structure so it appears consistently across README navigation paths.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants