fprime-component-checklist-review
Skill12k starsChanged 21 months agoApache-2.0View on GitHub
Fill in the F Prime Component Development Checklist (v1.2.0) for a component from automated evidence plus a short LLM review of the items no tool can prove. Maps every checklist item to its CodeQL query, component-checks script, review rule, or human step; defines the review rules CL-1..CL-8 for the residual items. Use when asked to run, fill, or audit the component checklist, or to review a component for flight readiness. Keywords: F Prime, checklist, component, flight software, CodeQL, component-checks, close-out, ISR, units, boundary tests.
Trending
More talk lately.about the whole repository
Who's talking about nasa/fprime
- Vibernets Streaming“Linux on Mars - NASA Mars Helicopter (අඟහරු ගිය Linux)”YouTube · Mar 3, 2021 · 12k views
- Suck Less | Tym Rabchuk“You Can Actually Build a Spacecraft With This #nasa #space #diy”YouTube · Jun 30, 2026 · 1.7k views
- こぶたNEWS“宇宙で初めての火星ヘリコプター”YouTube · Apr 10, 2021 · 741 views
- Marcia en Desplegando Cloud“🇪🇸#5.17 - Python en Acción (Podcast Charlas Técnicas de AWS)”YouTube · Nov 5, 2024 · 281 views
- Gourcer“Gource visualisation: nasa/fprime on 2021-04-22”YouTube · Apr 22, 2021 · 179 views
The biggest 5 of 71 mentions linking to the repository that our crawl found. Each line is their own headline.
See all 71
Talked about on GitHub, YouTube, Hacker News and the web (71 times).
On GitHub · 50
- Aug 19, 2026Add FPP (F Prime Prime) language — github-linguist/linguist15 reactions · 4 comments
- Sep 21, 2026Add New Darkmode UI Option — nasa/fprime-gds2 reactions
- Jul 31, 2025Deprecate serialize/deserialize in favor of [de]serialize[From/To] — nasa/fpp2 reactions · 1 comment
- Mar 19, 2026Add ConsoleNoWait — fprime-community/fprime-vxworks1 reaction
- Nov 22, 2025Merge release/v3.1.0a12 into release/v3.1.0 — nasa/fpp1 reaction
45 more on GitHub
- Oct 13, 2025Add ComAggregator for nasa/fprime#4264 — fprime-community/fprime-workshop-led-blinker1 reaction
- Dec 20, 2021FPP Visualization Automation — nasa/fprime-tools1 reaction · 5 comments
- Nov 10, 2026Svc/DpWriter: add processing override commands to force data product processing types on or off — lestarch-autobot/fprime0 reactions · 1 comment
- Oct 29, 2026Update for nasa/fprime#6174: add ComQueue drop-counter telemetry to packets — fprime-community/fprime-yamcs-reference0 reactions
- Oct 29, 2026Update for nasa/fprime#6174: add ComQueue drop-counter telemetry to packets — fprime-community/fprime-zephyr-reference0 reactions
- Oct 29, 2026Update for nasa/fprime#6174: add ComQueue drop-counter telemetry to packets — nasa/fprime-examples0 reactions
- Oct 28, 2026Update for nasa/fprime#6278: define FwTlmPacketizeOffsetType in TlmPacketizerCfg.fpp — fprime-community/fprime-zephyr-reference0 reactions
- Oct 28, 2026Restrict checkTimers and tlmWrite to having a single message on the q… — FireflySpace/fprime0 reactions
- Oct 24, 2026Upgrade to F Prime v4.4.1 — Open-Source-Space-Foundation/proves-core-reference0 reactions
- Oct 23, 2026TlmPacketizer: address lestarch-autobot review must-fix items (nasa/fprime#6144) — FireflySpace/fprime0 reactions
- Oct 16, 2026Include annotation for packets from FPP in dictionary — nasa/fpp0 reactions · 3 comments
- Oct 14, 2026Manual merge from nasa devel #5996 (pktType) — FireflySpace/fprime0 reactions
- Oct 12, 2026Svc/GenericHub: drop message with event and counter on allocation failure instead of asserting — JPL-Devin/fprime0 reactions · 1 comment
- Sep 30, 2026CI: fold workflow_dispatch runner/jobs inputs into the Ref and Framework matrices — JPL-Devin/fprime0 reactions · 1 comment
- Sep 22, 2026docs: import LED Blinker timeliness.md into website build — JPL-Devin/fprime0 reactions · 1 comment
- Sep 17, 2026Check C++ formatting — fprime-community/fprime-baremetal0 reactions
- Sep 14, 2026WasmSequencer: give the I32 host resume its own pause-check choice — JPL-Devin/fprime0 reactions · 1 comment
- Sep 11, 2026Fw/Types: serialize bool via U8 path and static-assert pointer size — JPL-Devin/fprime0 reactions · 1 comment
- Sep 1, 2026Rename LinuxUartDriver to PosixUartDriver with deprecated compatibility layer — JPL-Devin/fprime0 reactions · 2 comments
- Aug 22, 2026Feature: DFA-based structural health monitor app for telemetry channels — nasa/cFS0 reactions · 9 comments
- Jul 17, 2026Add TypeDemo component — fprime-community/fprime-yamcs-reference0 reactions
- Jun 22, 2026Add README.md and How-To guide for developing cFS F Prime applications — JPL-Devin/fprime_cfs_reference0 reactions · 2 comments
- Jun 16, 2026Use pr-xxxx pattern for GDS across Integration Test CI — JPL-Devin/fprime0 reactions · 3 comments
- May 29, 2026[#5159] ROSES - Student Review of Rule-Based Testing — lestarch-autobot/fprimesays it tested it0 reactions
- May 29, 2026[#5115] ROSES - Document how to decide between Active/Passive/Queued component - Student Review — lestarch-autobot/fprime0 reactions
- May 29, 2026[#5111] CCSDS Improvements — lestarch-autobot/fprime0 reactions
- May 29, 2026[#5099] DpCatalog Discards Status When Handling StateFile Database — lestarch-autobot/fprime0 reactions
- May 29, 2026[#5051] Add CI run exercising non-default FwType config values — lestarch-autobot/fprime0 reactions
- May 29, 2026[#5018] Replace hand-coded buffer and string classes with instantiated templates — lestarch-autobot/fprime0 reactions
- May 29, 2026[#4846] Add `fprime-util new --config-module` — lestarch-autobot/fprime0 reactions
- May 29, 2026[#4841] DpWriter always deallocates buffers to the same BufferManager — lestarch-autobot/fprime0 reactions
- May 29, 2026[#4806] Change fprime-gds serializable array type representation — lestarch-autobot/fprime0 reactions
- May 29, 2026[#4792] Consolidate Parameters ground scripts — lestarch-autobot/fprime0 reactions
- May 29, 2026[#4745] Update Core components to use FPP constants for string arguments — lestarch-autobot/fprime0 reactions
- May 29, 2026[#4711] fprime_test_api: Sometimes fprime_test_api does not connect to currently running fprime-gds session — lestarch-autobot/fprime0 reactions
- May 29, 2026[#4697] ROSES - Student Review of ISR pattern — lestarch-autobot/fprime0 reactions
- May 29, 2026[#4535] Configurable CPU Affinity for Subtopologies — lestarch-autobot/fprime0 reactions
- May 29, 2026[#4508] ROSES - Student review - Memory management — lestarch-autobot/fprime0 reactions
- May 29, 2026[#4454] VxWorks CI To Build All — lestarch-autobot/fprime0 reactions
- May 29, 2026[#4425] PrmDb filename in subtopology should be configurable — lestarch-autobot/fprime0 reactions
- May 29, 2026[#4324] Switch `FW_PACKET_COMMAND` enumerated value to non-zero value — lestarch-autobot/fprime0 reactions
- May 29, 2026[#4290] Clean up setup — lestarch-autobot/fprime0 reactions
- May 29, 2026[#4099] ROSES - Subtopologies (Working With) - Student Review — lestarch-autobot/fprime0 reactions · 1 comment
- May 29, 2026[#3662] ROSES - Add integration tests for fprime-examples repository — lestarch-autobot/fprime0 reactions
- May 29, 2026[#3565] Add local script to preview website rendering — lestarch-autobot/fprime0 reactions
On YouTube · 13
- Mar 3, 2021Linux on Mars - NASA Mars Helicopter (අඟහරු ගිය Linux) — Vibernets Streaming12k views · 50 comments
- Jun 30, 2026You Can Actually Build a Spacecraft With This #nasa #space #diy — Suck Less | Tym Rabchuk1.7k views · 2 comments
- Apr 10, 2021宇宙で初めての火星ヘリコプター — こぶたNEWS741 views · 3 comments
- Nov 5, 2024🇪🇸#5.17 - Python en Acción (Podcast Charlas Técnicas de AWS) — Marcia en Desplegando Cloud281 views · 2 comments
- Apr 22, 2021Gource visualisation: nasa/fprime on 2021-04-22 — Gourcer179 views
8 more on YouTube
- Feb 21, 2021Gource visualisation: nasa/fprime on 2021-02-21 — Gourcer157 views
- May 2, 2021Ferhell News 3 - Winget, WSL, Banimento da Universidade de Minessota e o Linux no Espaço! — Ferhell Linux & Techs117 views · 14 comments
- Jul 12, 2026GitHub - nasa/fprime: F´ - A flight software and embedded systems framework — GitHub Daily Trend AI Podcast95 views
- Feb 22, 2021Gource visualisation: nasa/fprime on 2021-02-22 — Gourcer70 views
- Oct 10, 2026NASA’s F Prime Turns Flight Software Into Components — Cochran Labs59 views
- Jul 2, 2026NASA fprime - A flight software — RandomTechAce37 views
- Jul 12, 2026nasa/fprime - Gource visualisation — Gourcer36 views
- Jul 4, 2026Почему эти 8 проектов уже изменили будущее? #Shorts — GitHub Находки3 views
On Hacker News · 6
- Feb 18, 2021The open source flight code that the NASA Mars drone is running68 points · 3 comments
- Feb 19, 2021Vue.js is powering NASA flight software4 points
- Jan 31, 2024NASA/fprime: F´ – A flight software and embedded systems framework2 points
- Jan 26, 2024F Prime – Flight software framework by NASA2 points
- Jan 21, 2024F': Ingenuity's Open-Source Flight Software Framework2 points
1 more on Hacker News
- Feb 1, 2024Fprime – A flight software and embedded systems framework by NASA1 point
On the web · 2
- Jul 12, 2026nasa/fprime: F´ - A f… - GitHub Daily Trend - Apple 팟캐스트 — podcasts.apple.com
- Jul 12, 2026nasa/fprime: F´ - A f... - GitHub Daily Trend — podcasts.apple.com
In this repository41 other files it gives its agents.
- AGENTS.mdAGENTS.md
- cmake/AGENTS.mdAGENTS.md
- docs/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- agent-skill-authoringSkill
- ai-session-reportSkill
- ai-session-summarySkill
- ci-test-runtime-policySkill
- fprime-checklist-closeoutSkill
- fprime-checklist-designSkill
- fprime-checklist-implementationSkill
- fprime-cmake-build-systemSkill
- fprime-component-design-fppSkill
- fprime-component-developmentSkill
- fprime-component-implementationSkill
- fprime-component-integration-testSkill
- fprime-component-requirementsSkill
- fprime-component-unit-testSkill
- fprime-cpp-designSkill
- fprime-fpp-navigationSkill
- fprime-ground-input-tracingSkill
- fprime-hardware-input-tracingSkill
- fprime-issue-risk-evaluationSkill
- fprime-iterative-developmentSkill
- fprime-maintenanceSkill
- fprime-requirements-reviewSkill
- fprime-run-for-recordSkill
- fprime-system-test-designSkill
- fprime-system-test-harnessSkill
- fprime-test-oracleSkill
- fprime-topology-developmentSkill
- fprime-unit-testingSkill
- jpl-design-principlesSkill
- maintainer-lookupSkill
- post-inline-reviewSkill
- pr-diff-scopingSkill
- prompt-injection-precheckSkill
- re-review-stateSkill
- triage-classifierSkill
- write-system-functional-docSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 31
N/A: only when the mapped check reports SKIP with a reason or the component has none of the construct (e.g.
- Distinctive: line 148
CL-3 Units in names (3.33): Every variable, member, parameter, FPP telemetry channel, and command argument that carries a physical quantity …
- Very specific: line 176
Run component-checks for the module (or read its published checks/summary.json) and the CodeQL SARIF for the branch.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
F Prime component checklist review
The checklist has 73 items in five sections. All but one are decided by tools; this skill tells you where each verdict comes from and defines the few judgements that remain for the reviewer.
Evidence sources
| Source | Where | Produces |
CodeQL (fprime/jpl-c-queries) | .github/codeql/fprime-queries/*.ql, run by codeql-jpl-standard.yml | SARIF alerts per rule id cpp/fprime/... |
| component-checks | nasa/fprime-actions/component-checks, run by component-checks.yml | <module>/checks/summary.json with ids R1..R9, D1..D10, I1..I4, U1..U5, C1..C3 |
| This skill | rules CL-1..CL-8 below | reviewer findings |
A checklist item is YES when every mapped rule/check passes for the
module, NO when any fails (cite the alert or check line in Notes),
N/A only when the mapped check reports SKIP with a reason or the
component has none of the construct (e.g. no ISR, no floats).
Item map
Legend: Q = CodeQL rule id (cpp/fprime/ prefix omitted), S = component-checks id,
L = review rule in this skill, H = human.
1 Requirements
| Item | Mechanism |
| 1.1 behaviours | S R9 (Kind column covers Behavior) + R1 (commands) + L CL-7 |
| 1.2 inputs | S R9 (Input) + R6 (ports) + R4 (parameters) |
| 1.3 outputs | S R9 (Output) + R2 (telemetry) + R3 (events) + R5 (data products) |
| 1.4 memory | S R9 (Memory, or waived in SDD) |
| 1.5 hardware I/O | S R9 (Hardware I/O, or waived) |
| 1.6 performance | S R9 (Performance, or waived) |
| 1.7 verification method | S R8 |
| 1.8 external ICD/FDD | S D9 (external-interfaces section or explicit None) |
2 Design
| Item | Mechanism |
| 2.1 high-level design | S check_sdd.py grade >= silver + L CL-8 |
| 2.2 block diagram | S D9 |
| 2.3 port table vs model | S D7 |
| 2.4 input-port behaviour | S D10 + L CL-8 |
| 2.5 port handlers | S D1 |
| 2.6 command handlers | S D2 |
| 2.7 sequence diagrams | S D9 |
| 2.8 state machines / use cases | S D9 |
| 2.9 state-machine actions | S D3 |
| 2.10 cmd/tlm/evr/prm tables | S D8 |
| 2.11 data-product tables | S D8 |
| 2.12 DP default priority | S D4 |
| 2.13 every port has a use case | S R6 + D10 |
| 2.14 port directions/types | S D7 |
| 2.15 component kind | S D9 |
| 2.16 requirements mapped to design | S D5 |
| 2.17 FPP compiles | S D6 |
3 Implementation
| Item | Mechanism |
| 3.1 CMake dependencies | S I1 |
| 3.2 no warnings | S I2 |
| 3.3 loops bounded | Q jpl-c/loop-bounds |
| 3.4 cyclic messages gated | Q unthrottled-cyclic-event |
| 3.5 switch default/break | Q switch-default, switch-case-fallthrough |
| 3.6 fallthrough annotated | Q switch-case-fallthrough |
| 3.7 variables local | Q global-mutable-variable |
| 3.8 access specifiers | Q public-data-member |
| 3.9 float equality | Q float-equality |
| 3.10 float precision / margins / loops | Q float-loop-control, float-narrowing + L CL-6 |
| 3.11 initialised before use | Q uninitialized-member + stock cpp/uninitialized-local |
| 3.12 DP priority configurable | S I3 |
| 3.13 command acknowledged | Q command-response |
| 3.14 validation failure returns | Q validation-failure-return |
| 3.15 internal port invoke() | Q internal-port-invoke |
| 3.16 pointer args asserted | Q checking-parameter-values |
| 3.17 state asserted | Q jpl-c/use-of-assertions-density |
| 3.18 no assert on HW/user input | Q assert-on-untrusted-input |
| 3.19 ISR no float | Q no-float-in-isr |
| 3.20 ISR minimal | Q isr-complexity |
| 3.21 ISR state before enable | L CL-1 |
| 3.22 ISR non-blocking | Q no-blocking-in-isr |
| 3.23 interrupt enables cleared at init | L CL-2 |
| 3.24 rate-group handlers non-blocking | Q no-blocking-in-sched-handler |
| 3.25 no file I/O in critical code | Q no-file-access-in-critical |
| 3.26 compound statements | Q compound-statements |
| 3.27 division guarded | Q division-guard, float-division-guard |
| 3.28 array bounds | Q unchecked-array-index, checking-parameter-values |
| 3.29 no nested function decl | Q no-function-decl-in-function |
| 3.30 for-header side effects | Q for-header-side-effects |
| 3.31 signed overflow | Q signed-overflow |
| 3.32 return values checked | Q jpl-c/checking-return-values |
| 3.33 units in names | L CL-3 |
| 3.34 named constants | Q magic-numbers, define-constant |
| 3.35 no printf | Q no-printf |
| 3.36 fixed-width types | Q jpl-c/basic-int-types |
| 3.37 static analysis | S I4 |
| 3.38 implementation matches reqs/design | L CL-4 |
4 Unit testing
| Item | Mechanism |
| 4.1 tests published | S U1 |
| 4.2 UT CMake dependencies | S U3 |
| 4.3 boundary tests | L CL-5 |
| 4.4 no leaks | S U4 |
| 4.5 coverage | S U5 |
5 Close-out
| Item | Mechanism |
| 5.1 no TBD/TODO/printf | Q incomplete-code, no-printf |
| 5.2 topology builds | S C1 |
| 5.3 runs on hardware | H performs the run; S C2 verifies docs/hardware-run.md |
| 5.4 SDD final | S D7, D8, D9, check_sdd.py |
| 5.5 CI passes | S C3 |
Review rules (residual LLM items)
Apply each rule only to the construct it names; report N/A when the
component has none. Cite file:line for every finding.
- CL-1 ISR state before enable (3.21). For every function matched by
the ISR naming convention (
*_isr,*interrupt_handler*,*_irq*) find the code that enables its interrupt (register write,request_irq,enableInterrupt, vector install). Every variable the ISR reads or writes must be assigned on a path that completes before that enable call. Finding:ISR state uninitialised(severity error). - CL-2 Interrupt enables cleared at init (3.23). In the component's
constructor/
init/configure/preamble, interrupt-enable bits must be explicitly cleared (or interrupts masked) before peripheral configuration, not assumed clear from reset. Finding:Interrupt enable assumed clear(warning). - CL-3 Units in names (3.33). Every variable, member, parameter, FPP
telemetry channel, and command argument that carries a physical quantity
(time, distance, angle, rate, temperature, voltage, current, size in bytes
vs words) must encode the unit in its name (
timeoutMs,angleRad,sizeBytes) or in an FPP@annotation. Finding:Missing unit in name(recommendation). - CL-4 Implementation matches requirements and design (3.38). For each
requirement row, locate the handler(s) that satisfy it and confirm the
behaviour, including each error path the SDD describes. Report any
requirement with no implementing code, and any handler behaviour the SDD
does not describe. Finding:
Implementation diverges from SDD(error). - CL-5 Boundary tests (4.3). For each bounded quantity in the model
(array sizes,
FW_ASSERTlimits, configuration constants, command-argument ranges, queue depths) there must be a unit test exercising the limit value and one past it. Finding:Boundary untested(warning). - CL-6 Float precision justified (3.10). Each
F32quantity must have sufficient precision for its range (e.g. seconds since epoch inF32loses seconds after ~190 days). Flag accumulators and time values held inF32. Finding:Insufficient float precision(warning). - CL-7 Requirement quality (1.1). Apply
fprime-requirements-reviewto the requirements table when it has changed in the PR. - CL-8 Design prose adequacy (2.1, 2.4). The SDD must describe, for each
input port and command, what the component does, including the rejection
path. Table rows alone do not satisfy this. Finding:
Behaviour not described(warning).
Procedure
- Run
component-checksfor the module (or read its publishedchecks/summary.json) and the CodeQL SARIF for the branch. - Fill sections 1, 2, 4, 5 and the Q/S rows of section 3 from that evidence.
- Apply CL-1..CL-8; fill the remaining rows.
- Item 5.3: confirm
docs/hardware-run.md(checked by C2) names a human tester; the run itself is not delegable. - Emit the checklist with status (
YES/NO/N/A) and Notes per the checklist's "Status Legend"; non-YESrows must carry the alert or check line that justifies them.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

