FHIR
Official@FHIR
FHIR hosts a nine-skill local development lifecycle suite covering feature requests, bug reports, planning, execution, review, GitHub issues, and pull requests.
Agent Skills by FHIR
Showing 9 vetted skills indexed across 1 GitHub repositories.
FHIRdev-pr-open
Pushes committed branches and opens draft pull requests on GitHub.
FHIRdev-issue
Publishes slot feature requests and bug reports as GitHub issues via gh CLI.
FHIRdev-approach
Generates three isolated solution approaches and a judged selection for feature requests or bug reports.
FHIRdev-report
Drafts and iterates structured bugreport.md files for local development defects.
FHIRdev-do
Executes implementation plans phase by phase with verified local commits.
FHIRdev-plan
Generates phased implementation plans from bug reports or feature requests.
FHIRdev-review
Runs dual engineering and QA review passes over a change scope and synthesizes findings into analysis.md.
FHIRdev-complete
Orchestrates the full local development loop from raw request to local commits.
FHIRdev-request
Drafts and iterates structured feature request markdown files as a staff-level Product Manager.
Frequently Asked Questions About FHIR
FAQPage SchemaWhat tasks can I complete using FHIR's dev skills?▼
The nine skills cover the full local inner loop: drafting feature requests and bug reports, judging three competing solution approaches, building phased implementation plans, executing code changes with local commits, running dual-track engineering and QA reviews, publishing GitHub issues, and opening pull requests.
Who are these skills designed for?▼
They target software engineers and engineering leads practicing structured local development. Each skill adopts a staff-level persona — Product Manager, Tech Lead, Engineering Lead, QA Lead, or release engineer — to produce reviewable artifacts like plan.md, analysis.md, and bugreport.md.
How do the skills run in practice?▼
Each skill accepts a full file path or a short slot number expanding to scratch/[MMDD]-[##]/. dev-complete chains request, approach, plan, do, and review in one invocation. GitHub publishing is opt-in via an AGENTS.md 'GitHub Integration' section with Enabled: yes.
What are the prerequisites and dependencies?▼
Skills operate on slot directories containing featurerequest.md, bugreport.md, plan.md, or analysis.md artifacts. GitHub issue and PR operations require the repository's AGENTS.md to carry a '## GitHub Integration' section with Enabled: yes; otherwise those skills do nothing.
Do these skills push code or modify my repository remotely?▼
Only dev-pr-open may push branches or open pull requests. dev-do commits locally but never pushes; dev-review is read-only against the codebase; dev-issue is the sole writer of GitHub issues. All remote operations stay user-initiated and opt-in.